text:
VCDA-3012: Allow specification of ssh key from KCP

In KCP, the ssh key can be specified under kubeadmConfigSpec as follows:
    users:
    - name: root
      sshAuthorizedKeys:
      - "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIAHCCo7SxtKx7o1SE2BfNiNsA+irrLyVYwtlvL4TUase akrishnakuma@vmware.com"

This results in the jinja script having the ssh key as part of the cloud init config itself. However the current way of converting the jinja script into a shell script and embedding it into the vcd cloud init does not work. Hence I did the following:

Parse the jinja and vcd cloudinit yaml files
Merge the yaml files
Treat the runcmd slightly specially (embed the runcmd of jinja into the vcd script)

Testing:
Created a cluster with my ssh key. After creating the dnat rule, the control plane node got the ssh key and was accessible. The worker nodes did not get the ssh key and were not accessible as a result.

This change is

controllers/vcdmachine_controller.go, line 879 at r1 (raw file):
Previously, sahithi (Sahithi Ayloo) wrote…
By "eating", you mean "appending"? At first, I thought it meant "deleting" :-)

I meant consuming :) Will change

controllers/vcdmachine_controller.go, line 888 at r1 (raw file):
Previously, sahithi (Sahithi Ayloo) wrote…
For my benefit, do the keys have exactly the same names in both the scripts? Could there be a different key name with the same intent?
For example "runcmd" ~ "executecmd" (or) "disable_root" ~ "disableroot"
Does cloud-init understand all of the other keys present in the Jinja script?

The "runcmd" is a cloudinit keyword and needs to be the same.

controllers/vcdmachine_controller.go, line 843 at r1 (raw file):
Previously, Anirudh9794 wrote…
Could the indentation be different for control plane and workers here? Just for my knowledge

It will be the same. Basically we are changing the write_files section, so it will always be 4

controllers/vcdmachine_controller.go, line 858 at r1 (raw file):
Previously, Anirudh9794 wrote…
won't cloudInitModified be empty if runcmd is not present in jinja?

No...so the __JINJA_RUNCMD_REPLACE_ME__ within cloudInitConfig will be replaced by "", so it will just be a blank line.

controllers/vcdmachine_controller.go, line 420 at r1 (raw file):
Previously, sahithi (Sahithi Ayloo) wrote…
Please include cluster name and worker node name as part of the log message

ACK

controllers/vcdmachine_controller.go, line 858 at r1 (raw file):
Previously, arunmk (Arun M. Krishnakumar) wrote…
No...so the __JINJA_RUNCMD_REPLACE_ME__ within cloudInitConfig will be replaced by "", so it will just be a blank line.

The above replacement will happen only if ok is true in jinjaRunCmd, ok := jinja["runcmd"] right?,

controllers/vcdmachine_controller.go, line 858 at r1 (raw file):
Previously, Anirudh9794 wrote…
The above replacement will happen only if ok is true in jinjaRunCmd, ok := jinja["runcmd"] right?,

otherwise, cloudInitModified will be ""


text:
[Multi-ESX] volume metadata file got deleted while removing volume from VM(placed on Esx2) which is in use by another VM(placed on Esx1)

Volume metadata file got deleted while removing volume from VM(placed on Esx2) which is in use by another VM(placed on Esx1); remove volume request deletes vmfd (metadata file) and volume properties (Filesystem, Disk Format, Created By, Created Date) got reset. Admin_CLI looses some important information that leads no information and bad experience to user.
Test bed setup:

2 ESX (E1 & E2) accessing a shared datastore SD1
2 VMs (VM1 & VM2):

VM1 is created on SD1 (registered at E1)
VM2 is created on SD1 (registered at E2)

Steps to reproduce (command + output for the reference)

create volume and validates its creation
mount volume from VM1 and validates its attachment state (leave it mounted)
remove the volume from VM2 (another vm from different ESX) and expects an error message saying volume is in use

Expectation: expects an error message saying volume is in use and no change in docker volume inspect & admin_cli volume ls
Current behavior: remove volume request deletes vmfd (metadata file) and volume properties (Filesystem, Disk Format, Created By, Created Date) got reset as shown below
# /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py volume ls
Volume  Datastore     VMGroup   Capacity  Used  Filesystem  Policy  Disk Format  Attached-to  Access      Attach-as               Created By  Created Date
------  ------------  --------  --------  ----  ----------  ------  -----------  -----------  ----------  ----------------------  ----------  ------------
vol2    sharedVmfs-0  _DEFAULT  100MB     15MB  N/A         N/A     N/A          detached     read-write  independent_persistent  N/A         N/A

command + output for the reference:

create volume and validates its creation

on VM1:

root@photon-xVmYMbyTn [ ~ ]#docker volume create -d vsphere vol2
vol2
root@photon-xVmYMbyTn [ ~ ]# docker volume ls
DRIVER              VOLUME NAME
vsphere:latest      vol2@sharedVmfs-0

on VM2:

root@photon-xVmYMbyTn [ ~ ]# docker volume ls
DRIVER              VOLUME NAME
vsphere:latest      vol2@sharedVmfs-0

on E1:
[root@sc2-rdops-vm05-dhcp-160-17:/vmfs/volumes/58f90ff7-dc27eee6-2501-020035a84afe/dockvols] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py volume ls
Volume  Datastore     VMGroup   Capacity  Used  Filesystem  Policy  Disk Format  Attached-to  Access      Attach-as               Created By   Created Date
------  ------------  --------  --------  ----  ----------  ------  -----------  -----------  ----------  ----------------------  -----------  ------------------------
vol2    sharedVmfs-0  _DEFAULT  100MB     13MB  ext4        N/A     thin         detached     read-write  independent_persistent  VM_17_SVMFS  Tue Apr 25 19:26:55 2017

[root@sc2-rdops-vm05-dhcp-160-17:/vmfs/volumes/58f90ff7-dc27eee6-2501-020035a84afe/dockvols] ls -la /vmfs/volumes/sharedVmfs-0/dockvols/11111111-1111-1111-1111-111111111111/
total 46104
drwxr-xr-x    1 root     root           980 Apr 25 19:29 .
drwxr-xr-x    1 root     root           420 Apr 25 19:12 ..
-rw-------    1 root     root          4096 Apr 25 19:29 vol2-2204c79fe109d3ae.vmfd
-rw-------    1 root     root     104857600 Apr 25 19:30 vol2-flat.vmdk
-rw-------    1 root     root           554 Apr 25 19:29 vol2.vmdk

mount volume from VM1 and validates its attachment state (leave it mounted)

on VM1:

root@photon-xVmYMbyTn [ ~ ]# docker run --rm -it -v vol2@sharedVmfs-0:/vol1 --name cnt_abc11 busybox
/ #     <<<<<<< leave it as mounted

on VM2:

root@photon-xVmYMbyTn [ ~ ]# docker volume inspect vol2@sharedVmfs-0
[
    {
        "Driver": "vsphere:latest",
        "Labels": null,
        "Mountpoint": "/mnt/vmdk/vol2@sharedVmfs-0",
        "Name": "vol2@sharedVmfs-0",
        "Options": {},
        "Scope": "global",
        "Status": {
            "access": "read-write",
            "attach-as": "independent_persistent",
            "attached to VM": "VM_17_SVMFS",
            "capacity": {
                "allocated": "15MB",
                "size": "100MB"
            },
            "clone-from": "None",
            "created": "Tue Apr 25 19:26:55 2017",
            "created by VM": "VM_17_SVMFS",
            "datastore": "sharedVmfs-0",
            "diskformat": "thin",
            "fstype": "ext4",
            "status": "attached"
        }
    }
]

on E1:

[root@sc2-rdops-vm05-dhcp-160-17:/vmfs/volumes/58f90ff7-dc27eee6-2501-020035a84afe/dockvols] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py volume ls
Volume  Datastore     VMGroup   Capacity  Used  Filesystem  Policy  Disk Format  Attached-to  Access      Attach-as               Created By   Created Date
------  ------------  --------  --------  ----  ----------  ------  -----------  -----------  ----------  ----------------------  -----------  ------------------------
vol2    sharedVmfs-0  _DEFAULT  100MB     15MB  ext4        N/A     thin         VM_17_SVMFS  read-write  independent_persistent  VM_17_SVMFS  Tue Apr 25 19:26:55 2017

remove the volume from VM2 (another vm from different ESX) and expects an error message saying volume is in use

on VM2:

root@photon-xVmYMbyTn [ ~ ]# docker volume rm vol2@sharedVmfs-0
Error response from daemon: Error while removing volume vol2@sharedVmfs-0: remove vol2@sharedVmfs-0: VolumeDriver.Remove: Failed to remove volume: Error caused by file /vmfs/volumes/58f90ff7-dc27eee6-2501-020035a84afe/dockvols/11111111-1111-1111-1111-111111111111/vol2.vmdk

on E1:

[root@sc2-rdops-vm05-dhcp-160-17:/vmfs/volumes/58f90ff7-dc27eee6-2501-020035a84afe/dockvols] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py volume ls
Volume  Datastore     VMGroup   Capacity  Used  Filesystem  Policy  Disk Format  Attached-to  Access      Attach-as               Created By  Created Date
------  ------------  --------  --------  ----  ----------  ------  -----------  -----------  ----------  ----------------------  ----------  ------------
vol2    sharedVmfs-0  _DEFAULT  100MB     15MB  N/A         N/A     N/A          detached     read-write  independent_persistent  N/A         N/A
[root@sc2-rdops-vm05-dhcp-160-17:/vmfs/volumes/58f90ff7-dc27eee6-2501-020035a84afe/dockvols] ls -la /vmfs/volumes/sharedVmfs-0/dockvols/11111111-1111-1111-1111-111111111111/
total 46096
drwxr-xr-x    1 root     root           840 Apr 25 19:32 .
drwxr-xr-x    1 root     root           420 Apr 25 19:12 ..
-rw-------    1 root     root     104857600 Apr 25 19:30 vol2-flat.vmdk
-rw-------    1 root     root           488 Apr 25 19:32 vol2.vmdk

vm_1_docker.txt
vm_2_docker.txt
vmdk_ops.txt

docker volume rm requests come from any VMs registered on E1 are not running into this issue, it is specific to multi-ESX setup.
output from another VM placed on E1:
root@photon-xVmYMbyTn [ ~ ]# docker volume rm vol2@sharedVmfs-0
Error response from daemon: Error while removing volume vol2@sharedVmfs-0: remove vol2@sharedVmfs-0: VolumeDriver.Remove: Failed to remove volume /vmfs/volumes/sharedVmfs-0/dockvols/11111111-1111-1111-1111-111111111111/vol2.vmdk, in use by VM uuid = 564d81f7-d886-7c9c-66f9-27c4d05875ba.
root@photon-xVmYMbyTn [ ~ ]# docker volume ls
DRIVER              VOLUME NAME
vsphere:latest      vol2@sharedVmfs-0
root@photon-xVmYMbyTn [ ~ ]# docker volume inspect vol2@sharedVmfs-0
[
    {
        "Driver": "vsphere:latest",
        "Labels": null,
        "Mountpoint": "/mnt/vmdk/vol2@sharedVmfs-0",
        "Name": "vol2@sharedVmfs-0",
        "Options": {},
        "Scope": "global",
        "Status": {
            "access": "read-write",
            "attach-as": "independent_persistent",
            "attached to VM": "VM_17_SVMFS",
            "capacity": {
                "allocated": "15MB",
                "size": "100MB"
            },
            "clone-from": "None",
            "created": "Tue Apr 25 19:26:55 2017",
            "created by VM": "VM_17_SVMFS",
            "datastore": "sharedVmfs-0",
            "diskformat": "thin",
            "fstype": "ext4",
            "status": "attached"
        }
    }
]

This is an issue on the esx disk libraries and already fixed for the next
up coming release of ESX. If needed we can request a backport to the
versions supported for the plugin.
.

@shuklanirdesh82 to add this to known issues.
@govint  to follow up with ESX folks to backport the fix to patch releases.

@govint write:

This is an issue on the esx disk libraries and already fixed for the next up coming release of ESX. If needed we can request a backport to the versions supported for the plugin.

What exactly is the "the issue in the ESX disklib"  ? Until it's backported (and backport deployed) we at least need to understand the specifics, and the way to fix it in our code if needed.
Reopening until the details are added.

Cross ESX multi tenancy feature is experimental.So pushing this issue to the back burner for now.

source: gharchive/issue

authors: govint msterin shuklanirdesh82 tusharnt

repo: vmware/docker-volume-vsphere

license_type: permissive

license_source: github-api


text:
LDAP Groups With Admin Privilege

LDAP Groups With Admin Privilege is not yet avialable. So if you enable LDAP you cannot connect as admin anymore

This setting is user settings, for user settings, you'd better login to the harbor web console to set it, ldap_group_admin_dn can be specified in harbor tile 1.7 web admin console.

But you cannot loggin to web admin console if you are not already an admin.
In our case we have automatized the harbor creation with the harbor bosh release and fix the ldap parameter inside the manifest. As soon as the ldap option is selected you can not log as admin.

authors: obeyler stonezdj

repo: vmware/harbor-boshrelease


text:
Update configuration API to accept rescan policy.

Involve work in both harbor-ui and harbor-adminserver.

fixed in #2667

repo: vmware/harbor


text:
args.vm_pwd should be args.vm_password

Describe the bug
The command execute_program_in_vm.py fails with
Traceback (most recent call last):
  File "commands/execute_program_in_vm.py", line 119, in <module>
    main()
  File "commands/execute_program_in_vm.py", line 70, in main
    username=args.vm_user, password=args.vm_pwd
AttributeError: 'Namespace' object has no attribute 'vm_pwd'
make: *** [Makefile:164: mkdir-artifacts] Error 1

Reproduction steps

Just the run the command

...
Expected behavior
Instead of using the args.vm_pwd use args.vm_password and the program will work fine
Additional context
No response

Fixed in https://github.com/vmware/pyvmomi-community-samples/pull/709

authors: DanielDraganov we-shall

repo: vmware/pyvmomi-community-samples

license_source: bigquery


text:
Update feature/roles-simplification with latest main

This PR updates the features/roles-simplification branch with the latest commits

This is required for #223
There is a conflict that will be solved in a separate commit
Do not squash & merge

I will prepare a better PR

source: gharchive/pull-request

repo: vmware/repository-service-tuf-cli

license: MIT


text:
改为异步，协程模式会不会性能更好？

起码有一个优点就是不会容易卡住。
系统复杂了，一个地方block就导致整个系统卡一下，可能很要命。
改为协程应该就没有这个隐患。它会把cpu让出来。

不会的，协程只能解决IO密集型任务，而量化实盘交易是典型的计算密集型任务，协程完全没用，而且因为不能保证事件调度的顺序，还会出现难以排查的隐形BUG

做成异步能优化线程之间调度的损耗，不过，这项目已经到这步了，改异步很难了。而且从开发的角度上来说，这对策略开发人员来说不太友好的

authors: hadrianl viponedream vnpy

repo: vnpy/vnpy

license: mit


text:
使用paper_account问题

连接实盘之后，在CTA策略初始化时，日志显示： 找不到底层接口：PAPER
请问，这个是正常的吗？

我们来查下，这个应该和历史数据查询有关系...请问用的什么交易接口呢？

BITMEX

试了下BINANCE初始化时，参数也未能初始化，可能和历史数据有关

用了Paper后，ChartWizard也报 找不到底层接口：PAPER ， 无法绘图，BINANCE

已在DEV分支修复，2.1.7发布后更新下就行

authors: vnpy yhmickey


text:
implement MatchQName() util func for CUD validators

Problem
Now, in current architecture
istructs.CUDValidator has Match() func to check if the validator matches

Problem (warm): validator should accept QNames only -> need to write boilerplate funcs that will simple compare the provided ICUDRow with the desired QName

Describe the solution you'd like
implement util func func MatchQName(qNames ...appdef.QName) func(cud ICUDRow, wsid WSID, cmdQName appdef.QName) bool and use it in places where only the validtor should be matched by CUD QNames only

Wrong way. No ability to check if wrong QNames are accidentally added. Will return back MatchFunc() and MatchQNames []Qname

repo: voedger/voedger


text:
Switch to official BetterReflection

Hi, I want to introduce some breaking changes to ondrejmirtes/better-reflection in a minor version. The package really shouldn't be used by anyone else rather than PHPStan, so please switch to the main repo, or create your own fork :) Thanks.

Turns out I don't have to do the big refactoring after all :) So there are no planned BC breaks in the near future. Switching to the official BetterReflection repo would still be a good idea though.

repo: voku/Simple-PHP-Code-Parser


text:
fix: compatible with TS 5.5

Feel free to restructure this or close this and fix it in another way. Mainly just to save you the debugging time on what changes.

Thanks for following up!

repo: volarjs/typescript-auto-import-cache


text:
Save changes of the entity a one tab

As I can save the changes an one tab of an entity each time the user caambie.
Example:
State
---Active
---Inactive
---Canceled
I want to save a record when the user makes the change of one of these options.
Sorry but I'm very new to this.

With date and user

You should override BeforeSave method of your SaveHandler, check (IsCreate || Old.State != Row.State) then set Row.WhoMadeChange = Convert.ToInt32(Authorization.UserId)

Please use slack channel for ask questions.
Join us on Slack
Get Invitation
Login

authors: VictorTomaili joheric volkanceylan

repo: volkanceylan/Serenity


text:
How to make one field in XXEnitityColume  just visible to special role

I have learned how to make one field just visible to special role in XXEntiyForm ,but how can I implement one field in XXEnitityColume  just visible to special role?

How did you do the first one?

Follow the tutorials of tenant ,which handle the field of tenantId Just follow this way.

I recommend using permissions for this. Assign a permission only to that role. Roles are only a set of permissions. Don't depend on them.

Navigasyon daha uygun yapılandırılmış edilemiyorsa, doğrudan veritabanına eklemek

Admin can be removed, it should be prohibited under the

@volkanceylan yes, I just want to make one field has a special read/write permission,how can I do this?

Look at the document, it's all over.

There is a topic about GetEditableFields in multi tenant guide. That is what you need.

authors: 107295472 ChenZhaobin volkanceylan zerodev


text:
Endpoint execution record

Hello,
Anyone has the experience with saving endpoint exectution record to database?
I have tried one, but has the problem with database connection.

below is my code
`namespace Mom.Sys.ServiceCallRecord
{
public class CallApplicationServiceLogMiddleware
{
    private readonly RequestDelegate _next;

    public CallApplicationServiceLogMiddleware(RequestDelegate next, IHostingEnvironment hostingEnvironment)
    {
        _next = next;
    }

    public string GetRequestString(HttpRequest request)
    {
        string requeststr = "";
        if (request.Method.ToLower().Equals("post"))
        {
            request.EnableRewind(); //启用倒带功能，就可以让 Request.Body 可以再次读取
            Stream stream = request.Body;
            byte[] buffer = new byte[request.ContentLength.Value];
            stream.Read(buffer, 0, buffer.Length);
            requeststr = Encoding.UTF8.GetString(buffer);
            request.Body.Position = 0;
        }
        else if (request.Method.ToLower().Equals("get"))
        {
            requeststr = request.QueryString.Value.ToString();
        }
        return requeststr;
    }
    public async Task InvokeAsync(HttpContext context)
    {
        HttpRequest request = context.Request;
        ServiceCallRecordRow serviceCallRecordRow = new ServiceCallRecordRow { };
        serviceCallRecordRow.ServiceCallRecordId = Guid.NewGuid();
        serviceCallRecordRow.RequestBody = GetRequestString(request);
        serviceCallRecordRow.IpAddress = context.Connection.RemoteIpAddress.ToString();
        serviceCallRecordRow.Url = request.Path.ToString();
        serviceCallRecordRow.Method = request.Method;
        serviceCallRecordRow.ExcuteStartTime = DateTime.Now;

        var originalBodyStream = context.Response.Body;
        using (var responseBody = new MemoryStream())
        {
            context.Response.Body = responseBody;
            await _next(context); //传递到下个管道

            serviceCallRecordRow.ResponseBody = await FormatResponse(context.Response);
            serviceCallRecordRow.ExcuteEndTime = DateTime.Now;
            using (var conn = SqlConnections.NewByKey("Mom")) {
                conn.Insert<ServiceCallRecordRow>(serviceCallRecordRow);
            }
            await responseBody.CopyToAsync(originalBodyStream);
        }
    }

    private async Task<string> FormatResponse(HttpResponse response)
    {
        response.Body.Seek(0, SeekOrigin.Begin);
        var text = await new StreamReader(response.Body).ReadToEndAsync();
        response.Body.Seek(0, SeekOrigin.Begin);

        return text;
    }
}

public static class CallApplicationServiceLogMiddlewareExtensions
{
    public static IApplicationBuilder UseRequestResponseLogging(this IApplicationBuilder builder)
    {
        return builder.UseMiddleware<CallApplicationServiceLogMiddleware>();
    }
}

}`
  app.UseRequestResponseLogging();//add this in Configure of startup

I work it out with using MiniProfilers.


text:
Patch to improve line editing some more

I've been using this patch to enable two "standard" bash-like bindings in pter -- Alt + d for del-word-right and Alt + Backspace for del-word-left.
For now these are treated specially, in the future perhaps pter could have full Alt-based bindings support. However, they are trickier than Ctrl-based ones, so for me just these two are enough. Plus we already have chain-based bindings, so no prob.
91-alt-backspace-alt-d.diff.gz
In addition, I've adjusted the patch from #36 to check if we're running under xterm-256color. The values for Ctrl + arrows/Delete seem to be specific to that terminfo config. (Alt-based ones from above seem to work with other terminfo configurations, such as screen-256color.)
30-ctrl-combos-should-be-conditional.diff.gz

I made the check for xterm a bit more generic and added a configuration option for the curses timeout. It defaults to 200ms, so you might want to update your configuration file, I assume based on the 100ms you used in the patch :)

I made the check for xterm a bit more generic and added a configuration option for the curses timeout.

Awesome!

I made the check for xterm a bit more generic

Yes, good idea, since pter also supports terminals with no color. I forgot about that.

I've pulled the latest changes and re-built the Docker image. With esc-delay still unset in the config, pter errors out:
[CRITICAL] Pter crashed with exception: 'int' object has no attribute 'isnumeric'
  File "/usr/local/lib/python3.11/dist-packages/pter-3.15.2.dev0-py3.11.egg/pter/curses.py", line 3119, in run_cursesui
    window.run()
  File "/usr/local/lib/python3.11/dist-packages/cursedspace-1.5.2-py3.11.egg/cursedspace/application.py", line 59, in run
    raise exception
  File "/usr/local/lib/python3.11/dist-packages/cursedspace-1.5.2-py3.11.egg/cursedspace/application.py", line 52, in run
    self.main()
  File "/usr/local/lib/python3.11/dist-packages/pter-3.15.2.dev0-py3.11.egg/pter/curses.py", line 1655, in main
    curses.set_escdelay(self.conf.number(common.SETTING_GROUP_GENERAL,
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/pter-3.15.2.dev0-py3.11.egg/pter/configuration.py", line 152, in number
    if value.isnumeric():
       ^^^^^^^^^^^^^^^

When esc-timeout is set, the crash goes away.

Yeah, should not have pushed that change 5 minutes before falling asleep, I suppose. It’s fixed!

Works great, thank you!

authors: andrei-a-papou vonshednob

repo: vonshednob/pter


text:
Add support for aborting execution without propagating any changes;

Enhancement idea.
When computed code modifies other fields in the model (which in turn triggers back the script) it can get unwieldy.
This adds a way to abort execution of the script without causing new computed value to re-trigger execution.
I used 'undefined' value in this PR (naturally this prevents the script from setting undefined value on the field).
What do you think?
Is 'null' better suited (or some other magic value)?

Thanks for the suggestion!
I find it hard to wrap my head around a proper usecase in which this is needed.
Next to that this is ofcourse a "dangerous" change since the plugin not execute the code if the value is set to something. That sounds like a major change and could add another Reserved word in the "Reserved words" section
Is an alternative maybe that we add it as an option in the plugin settings or is this only usefull if it's added as return value of the field?

I think basically the issue arises when you set value for the fields.
Changing a field causes the script to be fired again and again.
If you change more than one value a race condition frenzy starts and there is no safe exit strategy from the script.
Even returning the current value of the script field might fire the script again as there are other calls to script in progress.
I've noticed this in one of my more elaborate scripts.
I was lacking a way to tell the plugin that even though I was notified about a change I don't want to change anything (don't want to return a value for the field).
Maybe I can work around this by splitting the script into more hidden fields created just for the purpose of executing some code.

Closing as non-issue.
Preventing unwanted triggers when setting field values can be prevented by constructing fieldPath for setFieldValue method by concatenating two strings (field name split in two - so that the field name is not actually present in the code).

authors: gswierczynski velomovies

license: ISC


text:
Cannot build skybox.

Dear Group,
First of all i did this:

git clone https://github.com/vortexgpgpu/skybox.git

cd skybox

i change in toolchain_install.sh those: (for ubuntu 20.04 LTS)
#OSDIR=${OSDIR:=ubuntu/bionic}
OSDIR=${OSDIR:=ubuntu/focal}
#OS="${OS:=ubuntu/bionic}"
OS="${OS:=ubuntu/focal}"

./ci/toolchain_install.sh --all

source ./ci/toolchain_env.sh

i needed to add those third_party:
cocogfx
cvfpu
ramulator
berkeley-softfloat-3

after that i did make  and getting error:

$ make
make -C third_party
make[1]: Entering directory '/home/hardwaredesign/Desktop/skybox/skybox/third_party'
make -C cocogfx
make[2]: Entering directory '/home/hardwaredesign/Desktop/skybox/skybox/third_party/cocogfx'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/hardwaredesign/Desktop/skybox/skybox/third_party/cocogfx'
SPECIALIZE_TYPE=RISCV SOFTFLOAT_OPTS="-fPIC -DSOFTFLOAT_ROUND_ODD -DINLINE_LEVEL=5 -DSOFTFLOAT_FAST_DIV32TO16 -DSOFTFLOAT_FAST_DIV64TO32" make -C softfloat/build/Linux-x86_64-GCC
make[2]: Entering directory '/home/hardwaredesign/Desktop/skybox/skybox/third_party/softfloat/build/Linux-x86_64-GCC'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/hardwaredesign/Desktop/skybox/skybox/third_party/softfloat/build/Linux-x86_64-GCC'
cd ramulator && git apply ../../miscs/patch/ramulator.patch 2> /dev/null; true
make -C ramulator libramulator.a
make[2]: Entering directory '/home/hardwaredesign/Desktop/skybox/skybox/third_party/ramulator'
libtool -static -o libramulator.a  obj/WideIO2.o  obj/STTMRAM.o  obj/Controller.o  obj/LPDDR4.o  obj/LPDDR3.o  obj/HBM.o  obj/MemoryFactory.o  obj/Processor.o  obj/WideIO.o  obj/ALDRAM.o  obj/PCM.o  obj/Config.o  obj/TLDRAM.o  obj/GDDR5.o  obj/SALP.o  obj/DDR4.o  obj/DSARP.o  obj/StatType.o  obj/DDR3.o  obj/Cache.o  obj/Refresh.o obj/Gem5Wrapper.o
Usage: /usr/bin/libtool [OPTION]... [MODE-ARG]...
Try 'libtool --help' for more information.
libtool:   error: unrecognised option: '-static'
make[2]: *** [Makefile:39: libramulator.a] Error 1
make[2]: Leaving directory '/home/hardwaredesign/Desktop/skybox/skybox/third_party/ramulator'
make[1]: *** [Makefile:13: ramulator] Error 2
make[1]: Leaving directory '/home/hardwaredesign/Desktop/skybox/skybox/third_party'
make: *** [Makefile:2: all] Error 2

Is something wrong with my machine? or is there a code issue?
UPDATE: getting error from verilator now:
Update now  when i run the make -s getting error from verilator:
%Error: Internal Error: /home/hardwaredesign/Desktop/skybox/skybox/hw/rtl/core/VX_trace.vh:52:25: ../V3Scope.cpp:73: Can't locate varref scope
                                                                                : ... note: In instance '$unit'
   52 |     logic rd_float = 1'(rd >> 5) || 1'(rs2 >> 5);
      |                         ^~
                        /home/hardwaredesign/Desktop/skybox/skybox/hw/rtl/core/VX_dcr_data.sv:16:1: ... note: In file included from 'VX_dcr_data.sv'
                        /home/hardwaredesign/Desktop/skybox/skybox/hw/rtl/core/VX_core.sv:144:1: ... note: In file included from 'VX_core.sv'
                        /home/hardwaredesign/Desktop/skybox/skybox/hw/rtl/VX_socket.sv:333:1: ... note: In file included from 'VX_socket.sv'
                        /home/hardwaredesign/Desktop/skybox/skybox/hw/rtl/VX_cluster.sv:243:1: ... note: In file included from 'VX_cluster.sv'
                        /home/hardwaredesign/Desktop/skybox/skybox/hw/rtl/Vortex.sv:166:1: ... note: In file included from 'Vortex.sv'

After clean and build correct version tools need to add -fPIC commant in softfloat makefile to can be installed correctly.

repo: vortexgpgpu/skybox


text:
Set to default button does not update settings_screen

Default parameters are shown only after back to scanner_screen and after to settings_screen.
Perhaps flutter_settings_screens issue.

Created issue: https://github.com/GAM3RG33K/flutter_settings_screens/issues/121


text:
gpgkey cannot specify more than one of content, source

Affected Puppet, Ruby, OS and module versions/distributions

Puppet: 2019.8.5
Ruby: unsure
Distribution: Puppet Enterprise
Module version: 4.3.0

How to reproduce (e.g Puppet code you use)
puppet apply --modulepath /home/pat/modules -e 'class { "yum": manage_os_default_repos => false, }'

with the following added locally into the "yum" module. I understand that that is not the right way to do it. I only did it to create the smallest test case I could with the least amount of work.
I added the following to yum/data/common.yaml
yum::gpgkeys:
  /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7:
    source: puppet:///modules/yum/RPM-GPG-KEY-EPEL-7
yum::managed_repos:
  - 'local_epel'
yum::repos:
  local_epel:
    ensure: 'present'
    descr: 'EPEL for RHEL7'
    baseurl: 'http://reposerver.vanguard.com/epel7/'
    enabled: true
    gpgcheck: true
    gpgkey: 'file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7'

I created a "files" dir in "yum" module and I added the gpg key file from EPEL to yum/files directory
What are you seeing
Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, You cannot specify more than one of content, source (file: /export/home/nt018238/puppet/dev/modules/yum/manifests/gpgkey.pp, line: 50, column: 18) (file: /export/home/nt018238/puppet/dev/modules/yum/manifests/init.pp, line: 140) on node xyz.vanguard.com

What behaviour did you expect instead
I expected

the file /etc/yum.repos.d/local_epel.repo to be created with content enabling gpg key and pointing to file in /etc/pki/rpm-gpg
the file /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7 to be created from files dir within module
rpm --import to run for the file created in /etc/pki/rpm-gpg

Output log
See "What are you seeing above"
Any additional information you'd like to impart
I feel as though I have crafted my yaml correctly to accomplish my goal following the examples in the README. What have I done wrong to cause this compilation/evaluation error?
Sorry if I am using the "issue tracker" here inappropriately. Wasn't sure if this was an acceptable use
First time posting an "issue" on github. I wanted to assign the "question" label to this "issue". I can't seem to do that. Are labels only applied by the project owners?

I figured out what I was doing wrong. Because /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-* exists in the module data, the merge of my hieradata, which specified "source", was duplicating data provided by the module data causing the error. I simply needed to remove the "source" line from my hieradata. Sorry for wasting anyone's time with this question/issue

repo: voxpupuli/puppet-yum


text:
Server translates error object thrown from method into SOAP Fault

A service method can send back a SOAP Fault response to a client by throwing an object that contains a Fault property.
Note that the generated XML uses the "soap" NS that is defined by the _envelop method.
It isn't the best option but I don't know how to do better. I gave a quick look at wsdl.js but ran away ;-)

Thanks a lot for your contributions @mdhooge - we appreciate it a lot :+1:
Before we can merge this, I'll have to ask you to squash your commits into a single one, like it's described in our Guidelines for Submitting a Pull Request (this is also necessary for your follow up PR at #558)

Hi,
I'm not very good at pushing changes for PRs! I removed a branch, so PR558 is closed. :-(
However I created branches PR557 & PR558; with PR557 == PR558~1 and PR558 == master.
And, good news, both commits still pass the tests.
There is one test ("should not append :80 to the Host header...") that doesn't pass, but it was already the case before my changes.
Cheers

Oh, that's a pitty @mdhooge, sorry for this inconvenience, but I have to insist on the "one Commit per Pull Request" rule here at node-soap. See the excellent GitHub Help on Git Rebase and GithHub Help on Using Git Rebase for further information. Thanks.

OK, so it was simpler to create a new PR.
And because #558 needs that one to be applied, I'll wait for you to merge it first.
Cheers

authors: herom mdhooge

repo: vpulim/node-soap


text:
[Feature Request] Add Recently used display names to a friend

Sometimes you have friends which keep updating their display name. While you can see the changes in the friend log, it would be helpful if you could see previuously used names inside VRCX.
Something like Steam's "This user also played as (...)"

that seems to be a thing already

Yeah this already exists, VRCX just needs to log the friend that changed their name though. VRCX can't get that data from the network

authors: BLANKE1 EinDev TayouVR

repo: vrcx-team/VRCX


text:
Remove values from rucio.cfg

This PR removes parameters from the rucio.cfg that might cause the CLI to refresh the token unintentionally and sets the extension to use the token directly from the environment variable.

ping @egazzarr

repo: vre-hub/vre


text:
有一个小小的请求

请坐一个动态背景 蟹蟹

好的没问题~ 下次请把需求写在标题上哦~

authors: vrilc yanfengeiya

repo: vrilc/piggy


text:
Support for Workspace Settings is broken

[x] I'm sure this issue is not a duplicate.

Extension will fail to load if both User Settings and Workspace Settings contains entry vsicons.associations.files (or vsicons.associations.folders)

Devtools console log
Activating extension `robertohuertasm.vscode-icons` failed:  TypeError: Cannot assign to read only property 'files' of object
t.log @ console.ts:136
t._logExtensionHostMessage @ extensionHost.ts:391
(anonymous) @ extensionHost.ts:209
emitTwo @ events.js:126
emit @ events.js:214
emit @ internal/child_process.js:772
_combinedTickCallback @ internal/process/next_tick.js:141
_tickCallback @ internal/process/next_tick.js:180
console.ts:136 [Extension Host] Here is the error stack:  Error: TypeError: Cannot assign to read only property 'files' of object
	at Object.set (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:565:575)
	at Object.getVsiconsConfig (D:\Soft\VSCode\data\extensions\robertohuertasm.vscode-icons-7.25.0\out\src\utils\vscode-extensions.js:15:41)
	at Object.<anonymous> (D:\Soft\VSCode\data\extensions\robertohuertasm.vscode-icons-7.25.0\out\src\commands\index.js:18:47)
	at Object.<anonymous> (D:\Soft\VSCode\data\extensions\robertohuertasm.vscode-icons-7.25.0\out\src\commands\index.js:271:3)
	at Module._compile (module.js:642:30)
	at Object.Module._extensions..js (module.js:653:10)
	at Module.load (module.js:561:32)
	at tryModuleLoad (module.js:504:12)
	at Function.Module._load (module.js:496:3)
	at Function.t._load (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:831:951)
	at Function.o._load (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:781:881)
	at Module.require (module.js:586:17)
	at require (internal/module.js:11:18)
	at Object.<anonymous> (D:\Soft\VSCode\data\extensions\robertohuertasm.vscode-icons-7.25.0\out\src\init\welcome.js:9:20)
	at Object.<anonymous> (D:\Soft\VSCode\data\extensions\robertohuertasm.vscode-icons-7.25.0\out\src\init\welcome.js:73:3)
	at Module._compile (module.js:642:30)
	at Object.Module._extensions..js (module.js:653:10)
	at Module.load (module.js:561:32)
	at tryModuleLoad (module.js:504:12)
	at Function.Module._load (module.js:496:3)
	at Function.t._load (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:831:951)
	at Function.o._load (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:781:881)
	at Module.require (module.js:586:17)
	at require (internal/module.js:11:18)
	at Object.<anonymous> (D:\Soft\VSCode\data\extensions\robertohuertasm.vscode-icons-7.25.0\out\src\init\index.js:6:10)
	at Object.<anonymous> (D:\Soft\VSCode\data\extensions\robertohuertasm.vscode-icons-7.25.0\out\src\init\index.js:10:3)
	at Module._compile (module.js:642:30)
	at Object.Module._extensions..js (module.js:653:10)
	at Module.load (module.js:561:32)
	at tryModuleLoad (module.js:504:12)
	at Function.Module._load (module.js:496:3)
	at Function.t._load (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:831:951)
	at Function.o._load (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:781:881)
	at Module.require (module.js:586:17)
	at require (internal/module.js:11:18)
	at Object.<anonymous> (D:\Soft\VSCode\data\extensions\robertohuertasm.vscode-icons-7.25.0\out\src\index.js:5:14)
	at Object.<anonymous> (D:\Soft\VSCode\data\extensions\robertohuertasm.vscode-icons-7.25.0\out\src\index.js:51:3)
	at Module._compile (module.js:642:30)
	at Object.Module._extensions..js (module.js:653:10)
	at Module.load (module.js:561:32)
	at tryModuleLoad (module.js:504:12)
	at Function.Module._load (module.js:496:3)
	at Function.t._load (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:831:951)
	at Function.o._load (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:781:881)
	at Module.require (module.js:586:17)
	at require (internal/module.js:11:18)
	at Function.i [as __$__nodeRequire] (d:\Soft\VSCode\resources\app\out\vs\loader.js:30:770)
	at d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:807:367
	at t._doActivateExtension (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:807:479)
	at t._activateExtension (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:806:337)
	at Object.actualActivateExtension (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:804:204)
	at e._activateExtension (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:459:497)
	at d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:459:116
	at Array.map (<anonymous>)
	at e._activateExtensions (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:459:91)
	at e.activateByEvent (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:457:367)
	at t.activateByEvent (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:804:568)
	at t.handleEagerExtensions (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:828:359)
	at d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:827:570
	at Object.g [as _notify] (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:77:971)
	at Object.enter (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:81:277)
	at n.Class.derive._oncancel._run (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:83:100)
	at n.Class.derive._oncancel._completed (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:82:559)
	at e.open (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:113:375)
	at d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:804:242
	at Object.g [as _notify] (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:77:971)
	at Object.enter (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:81:277)
	at n.Class.derive._oncancel._run (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:83:100)
	at n.Class.derive._oncancel._completed (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:82:559)
	at c (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:85:1011)
	at $.then.o.(anonymous function) (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:86:205)
	at Object.g [as _notify] (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:77:971)
	at Object.enter (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:81:277)
	at n.Class.derive._oncancel._run (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:83:100)
	at n.Class.derive._oncancel._completed (d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:82:559)
	at d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:117:1020
	at d:\Soft\VSCode\resources\app\out\vs\workbench\node\extensionHostProcess.js:150:661
	at LOOP (original-fs.js:1757:14)
	at _combinedTickCallback (internal/process/next_tick.js:131:7)
	at process._tickCallback (internal/process/next_tick.js:180:9)

Extension version: 7.25.0
VS Code version: Code 1.26.1 (493869ee8e8a846b0855873886fc79d480d342de, 2018-08-16T18:38:57.434Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4430 CPU @ 3.00GHz (4 x 3000)

GPU Status
2d_canvas: enabledchecker_imaging: enabled_force_onflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_force_onnative_gpu_memory_buffers: enabledrasterization: enabled_forcevideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.93GB (12.06GB free)

Process Argv
D:\Soft\VSCode\Code.exe

Screen Reader
no

VM
67%

We are aware and preparing a fix with our next major update

repo: vscode-icons/vscode-icons


text:
Current file name in % register is invalid

The percent register % has an invalid file name which makes it unusable.
For example, I wanted to quickly run my current file through node, so I ran the following command:
:! node %

which got expanded as:
VSCode-Neovim:

:! node __vscode_neovim__-file:///Users/path/to/my/file.js

That prefix obviously made the command fail. Is that a hard requirement to have to make this extension work?

% is referring to the scratch buffer, see https://github.com/vscode-neovim/vscode-neovim#-how-it-works. I have my doubts this can be fixed.

Thanks for the link @trkoch, I understand the difficulty around this. The plugin makes vscode 10x better IMO 😄 but I ran into the same issue wanting to run updates on a csproj-file in .Net.

Perhaps a Neovim plugin inlined in this extension could override % and remove the prefix? @asvetliakov Perhaps you can give us some hints as to why this prefix is required in the first place?

is there a way to get the file path in nvim by any means?
In vscode one can use the predefined variables
Is there a way to use these variables in nvim ?

This is my current workaround for this issue. I named the script vnr (say 'vscode neovim replace'). If you prefix your command with vnr, it'll strip out __vscode_neovim__-file:// then run your command.
https://gist.github.com/ambiguous48/234df06b9b915feead215152b78f92e4
# instead of this
:! node %

# do this
:! vnr node %

Note: you probably want to place this in your PATH so you can reference it directly.

@thenbe Your solution is working great, thanks! It just seems like your link is broken, this one should work: https://gist.github.com/thenbe/234df06b9b915feead215152b78f92e4
An example of a mapping I created: nnoremap <buffer> <Leader>r :exec '!vnr python3' shellescape(@%, 1)<CR>

authors: DiogoDoreto ambiguous48 filchristou infinitewhileloop niklaswallerstedt trkoch

repo: vscode-neovim/vscode-neovim


text:
Drop warning about RPM support

I'm using this module on CentOS 6 and 7, and it works perfectly, so you can probably drop the warning. Your metadata.json is already correct.

Thank you for the feedback and the pull request!

repo: vshn/puppet-gitlab


text:
fix: avoid registering disposables repeatedly (#48)

I think this fixes #48.
disposables were only being dispose()'d when showMarkers was false, but were otherwise being added to the decorators every time showMarkers was evaluated true. This caused the hover providers to be registered several times... and potentially causing other issues that I have not investigated (that onDidChangeActiveTextEditor decorator there)

Thanks so much!

Happy to help!

authors: alvaromartmart lostintangent

repo: vsls-contrib/codetour


text:
added "GradientProgressBar" to category "Activity Indicator"

added "GradientProgressBar"

Project URL
https://github.com/fxm90/GradientProgressBar
Description

added "GradientProgressBar" to category "Activity Indicator"

Why it should be included to awesome-ios (optional)
Checklist

[ ] Only one project/change is in this pull request
[ ] Addition in chronological order (bottom of category)
[ ] Supports iOS 9 / tvOS 10 or later
[ ] Supports Swift 3
[ ] Has a commit from less than 2 years ago
[ ] Has a clear README in English

          1 Warning

:warning:
Please update the Pull Request title to contain the library name

  Generated by :no_entry_sign: Danger

Hey @fxm90, thanks for contributing 👍

authors: danger-awesome-ios fxm90 lfarah

repo: vsouza/awesome-ios


text:
Add MirrorDiffKit

Add MirrorDiffKit to the section for "Other testing."
Project URL

https://github.com/Kuniwak/MirrorDiffKit
Description

Add MirrorDiffKit to the section for "Other testing."
Why it should be included to awesome-ios (optional)
Major assertion libraries such as XCTest or Nimble usually print a text that is hard to read.
But you can see pretty diff between any structs or any classes or any values if you use MirrorDiffKit.
For example, the following output by XCTest:
XCTAssertEqual failed: ("Example(key1: "I\'m not changed", key2: "I\'m deleted")") is not equal to ("Example(key1: "I\'m not changed", key2: "I\'m inserted")")

becomse like the following:
struct Example {
    key1: "I'm not changed"
  - key2: "I'm deleted"
  + key2: "I'm inserted"
}

by the function diff(between: Any, and: Any).
This feature is very useful but major assertion libraries do not support this feature yet.
So, I think this library is awesome.
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 3
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

Hey @Kuniwak nice lib, thanks for contributing to awesome-ios😀

Thanks a lot!


text:
Wormholy

Added Wormholy
Added library Wormholy
Project URL
https://github.com/pmusolino/Wormholy
Category
Debugging
Description
A new network debugging library.
Why it should be included to awesome-ios (optional)
Start debugging iOS network calls like a wizard, without extra code! Wormholy makes debugging quick and reliable.
Checklist

[x] Only one project/change is in this pull request
[x] Has unit tests, integration tests or UI tests
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Please update the Pull Request title to contain the library name

  Generated by :no_entry_sign: Danger

Hey @pmusolino, thanks for contributing! Unfortunately, we cannot merge your PR since Wormholy doesn't have tests. Please add some tests and open a new PR

authors: danger-awesome-ios lfarah pmusolino


text:
iOS 9

Looks to not be available in iOS9 - any ideas? Thanks.

+1 Has anyone been able to get this working in iOS9? It works perfectly in 8.4. Any help would be much appreciated. Thanks.

It should work. iOS 9 changed how custom URL are handled: you need to explicitly white list custom URLs e.g. instagram:// for this plugin to work
You can modify your *-Info.plist file in /platforms/ios, but that's a generated file. Alternatively, I think you can make a custom plugin which generates the correct values in the .plist file
See link

We can handle this from within this plugin by adding a config-file element in the iOS section of the plugin.xml.
<config-file target="*-Info.plist" parent="CFBundleURLTypes">
    <array>
        <dict>
            <key>key</key>
            <string>value</string>
        </dict>
    </array>
</config-file>

We just need the relevant key and value.

Oh right :P
This works for me:
<platform name="ios">
  <config-file target="*-Info.plist" parent="LSApplicationQueriesSchemes">
    <array>
      <string>instagram</string>
    </array>
  </config-file>
</platform>

However, previous values in LSApplicationQueriesSchemes should not be overwritten. Not sure how to do that.

Looking at plugman source code, and it seems that when the plist is updated all values are merged instead of overwritten. So, I would say that just adding the snippet to the plugin.xml is the right thing to do to fix the functionality for iOS9.
@sfrdmn, would you make a pull request?

authors: ErikAugust sfrdmn vstirbu yodarjun

repo: vstirbu/InstagramPlugin


text:
Home page - Navigation Menu

Traduction de la page d'accueil et du menu.
J'ai repris l'idée du "Le Framework JavaScript Évolutif" pour "The Progressive JavaScript Framework".
Deux trois petits trucs que je ne suis pas sur de la nécessité de traduire :

17kb min+gzip Runtime
Template -> Modèles ? (Menu écosystème)

Je vais merge ta pull request et faire les ajustements pour présenter quelque chose à l'adresse : https://vuejs-fr.github.io/vuejs.org/ en attendant la redirection CNAME.
On peut rediscuter de mes coms si tu le souhaites !

authors: Haeresis zyhou


text:
Toutes les traductions de la documentation pour la v2.6

Bonjour à tous, je viens de mettre à jour le site avec les nouveautés de sa version anglaise. J'ai traduit toutes les nouveautés assez rapidement aussi j'aurais besoin de votre aide pour des corrections orthographique ou remaniement de phrase si j'ai fait des contresens !

Merci à @forresst, @darenju, @Kocal ainsi que @Giildo pour vos retours !
J'avais pas le temps de me relire, vous avez été top !
Je laisse encore un peu ouverte la PR et je mergerais demain ou jeudi histoire d'avoir une doc à jour même avec quelques coquilles. Ça n'empèchera biensûr personne de proposer des corrections après :)

Merci à tous ! Je monte ça en ligne. S'il reste des erreurs, n'hésitez pas à PR !


text:
fix(reactivity): export MarkRaw type

closes #7048
Reproduction: https://github.com/sxzz/vue-issue-markRaw
src/main.ts:3:14 - error TS4023: Exported variable 'foo' has or is using name 'RawSymbol' from external module "/path/vue-issue-markRaw/node_modules/.pnpm/@vue+reactivity@3.2.37/node_modules/@vue/reactivity/dist/reactivity" but cannot be named.

3 export const foo = markRaw({ key: 'value' })
               ~~~

There seem to be more types that are being reported as missing by api-extractor.
I wonder if some of these should be exported but prefixed with an _ and marked as @internal so we don't expose types that aren't meant to be used in userland like this one.

authors: posva sxzz

repo: vuejs/core


text:
fix(compiler-core): pass _cache to ssr render functions

despite the diff, this is a very brief fix. we were relying on (but omitting to pass) the _cache argument in ssr, meaning in some cases v-once would generate code that relied on an object that wasn't present. Test added.
resolves #7644

This isn't the right fix, since _cache isn't actually passed to ssrRender in server-renderer. The better fix is disabling v-once transform which is unnecessary during SSR anyway. See 05f94cf7

Thank you!
In local testing I found that an empty object was being passed in the _cache slot - what was that?

@danielroe I discovered those were additional arguments originally passed for an optimization attempt, but were accidentally left when I abandoned that attempt. They are now removed in 2a9e3796


text:
TypeError: Cannot read properties of null

Type: Bug
It seems that volar does not find plugins in monorepo environments
2023-03-06 11:53:59.449 [error] TypeError: Cannot read properties of null (reading 'indexOf')
	at <HOME>\.vscode\extensions\vue.volar-1.2.0-win32-x64\dist\node\client.js:59:428
	at Array.some (<anonymous>)
	at <HOME>\.vscode\extensions\vue.volar-1.2.0-win32-x64\dist\node\client.js:59:418
	at Generator.next (<anonymous>)
	at a (<HOME>\.vscode\extensions\vue.volar-1.2.0-win32-x64\dist\node\client.js:42:39708)

volar doctor
Error loading webview: Error: Could not register service workers: InvalidStateError: Failed to register a ServiceWorker: The document is in an invalid state..

Extension version: 1.2.0
VS Code version: Code 1.76.0 (92da9481c0904c6adfe372c12da3b7748d74bdcb, 2023-03-01T10:22:44.506Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 7 PRO 5875U with Radeon Graphics      (16 x 1996)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
46.80GB (26.30GB free)

Process Argv
--crash-reporter-id 2ecdc59c-7d55-48a0-beaf-451bf71a6cf4

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vscaat:30438848
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848:30662994
nodejswelcome1:30587005
282f8724:30602487
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
2i9eh265:30646982
showlangstatbar:30672706
vsccsb:30677849
pythonms35cf:30676801

Got a similar error that terminate the extension host of VSC
2023-03-09 15:17:38.585 [error] TypeError: Cannot read properties of null (reading 'indexOf')
    at /Users/me/.vscode/extensions/vue.volar-1.2.0-darwin-x64/dist/node/client.js:59:428
    at Array.some (<anonymous>)
    at /Users/me/.vscode/extensions/vue.volar-1.2.0-darwin-x64/dist/node/client.js:59:418
    at Generator.next (<anonymous>)
    at a (/Users/me/.vscode/extensions/vue.volar-1.2.0-darwin-x64/dist/node/client.js:42:39708)

Thanks for the report, it should be fixed with the latest commits, you can update to 1.3.x pre-release for now to avoid the error.

repo: vuejs/language-tools


text:
Provide a way to disable warnings for "No match found"

What problem is this solving
At the moment, the router logs a "No match found" warning that cannot be disabled when it tries to resolve a route that doesn't exit.
There are more complex routing scenarios where the creation of initial routing table or the addition of a new route requires a check whether a route already exists, by calling the router instance's resolve method. The warning impairs the development cycle by polluting the log (both on client and server in an SSR context).
As an example, think of an SSR app with a backend where admin users can create additional redirects or aliases to hardcoded routes in the administration panel.
Proposed solution
Add a flag, disableWarnings, in the createRouter factory method to disable these kinds of warnings.
Describe alternatives you've considered
No response

Duplicate of https://github.com/vuejs/router/issues/359

Please, search existing issues and pull requests before opening issues, it saves maintainers a lot of time 🙏

authors: hokkaido posva

repo: vuejs/router


text:
If the search is not set, an error will appear

If algolia is not set，the following error message will appear

Fixed by #47

authors: Jinjiang shibin-cli

repo: vuejs/theme


text:
Opera 浏览器 扩展商店中无法下载 vue-devtools，能否在商店中上传vue-devtools？

Version
5.3.3
Browser and OS info
Opera 67 / macOS
Steps to reproduce
https://addons.opera.com/zh-cn/
商店中找不到 vue-devtools
What is expected?
可以在 Opera 浏览器使用 vue-devtools
What is actually happening?
商店中找不到 vue-devtools

谢谢！

vue-devtools is not publish in the opera store
you can use the  manual installation guide to install on opera
opera is almost chrome

authors: hulkyhawk varjay

repo: vuejs/vue-devtools


text:
vue add @vue/unit-jest报错

几位好，这个仓库只会讨论一些零散的非正式的中文文档翻译，不讨论技术本身。
cli 的技术问题反馈请移步至：https://github.com/vuejs/vue-cli 或其它技术论坛和问答社区。这些地方有更多更活跃的人可以帮到大家。
更何况 cli 的中文文档也已经“转正”了：https://cli.vuejs.org/
因此这里对该 issue 做关闭处理。
感谢理解

authors: Jinjiang verybigorange

repo: vuejs/vue-docs-zh-cn


text:
Add parserOptions.vueFeatures.interpolationAsNonHTML option

This PR adds the parserOptions.vueFeatures.interpolationAsNonHTML option. When the option is enabled, the interpolation is parsed as non-HTML.
This option is disabled by default (it works the same as before).
Enabling this option by default is breaking change and requires a major version upgrade. Also, major version upgrades may need to add options for Vue 3, such as disabling filter parsing.
refs https://github.com/vuejs/eslint-plugin-vue/issues/370

@ota-meshi setting parserOptions.vueFeatures.interpolationAsNonHTML to true doesn't disable the error when using greater than or less than in conditional statements.
  parser: 'vue-eslint-parser',
  parserOptions: {
    vueFeatures: {
      interpolationAsNonHTML: true,
    },
  },

            <VIcon
              v-if="activities?.length > 1"
              icon="mdi-menu-down"
            />

Closing tag highlights in red.

repo: vuejs/vue-eslint-parser


text:
feat(runtime-core): dom-specific getFallthroughAttrs to runtime-dom

It doesn't feel right to have checks for 'style' and 'class' in runtime-core. Ideally it should be render-independent.
This PR would also allow custom renderers to provide their own implementation.

Thanks for your feedback! Requested changes have been done.

repo: vuejs/vue-next


text:
Add mixin option to Vue Router

What problem does this feature solve?
I need to be able to add a mixin only for components which are directly instantiated inside the , not their children.
At this time, it seems to me that I have to go inside each of those components and add a mixin manually, which I would like to avoid.
What I've done is to create a global mixin with a beforeCreate lifecycle event, but it's triggered for every component that's loaded, which I also would like to avoid.
What does the proposed API look like?
import mixin from 'mixin';
interface RouteConfig = {
...
mixins?: any // Mixin to be applied when instantiating a component
}

This belongs to the user land: it can be achieved with a function rewriting the routes array before passing it to the router or, as you said, manually passing the mixin to the different view components.

Hello and thank you for your response, but I'm not sure that I follow.
Let's say I have a file named: routerMixin.js
export default {     beforeCreate() {         console.log('beforeCreate');     } };
My routes are configured like this:
`import routerMixin from '../util/routerMixin';
const routes = [
{
path: '/login',
name: 'Login',
component: () => import(/* webpackChunkName: "login" */ '../views/Login.vue'),
mixins: [routerMixin]
}]`
And nothing happens, mixin is not executed, and it's not accessible from the loaded component

repo: vuejs/vue-router


text:
Dynamic values in array undefined in props ready method

Vue.js version
1.0.26
Reproduction Link
http://jsfiddle.net/qta4ny91/
Steps to reproduce
What is Expected?
Have the dynamic array value props available in the components ready method.
What is actually happening?
The dynamic array value props are undefined.

That's working as expected since the array is intantiated while the stats object is still empty (because of the timeout)
I think you're looking to do something like this: http://jsfiddle.net/u7ydz6cp/

If you open the console, you can see that the values are still undefined. Even when I remove the timeout it's still undefined. http://jsfiddle.net/7eyg09v2/

@avanerk That's because the ready hook is fired after the compilation: http://vuejs.org/guide/instance.html#Lifecycle-Diagram
You can use beforeCompile but I recommend you using either a computed property or a method

authors: avanerk posva

repo: vuejs/vue


text:
how to pass propsData to async component

// ayncA.js
import Vue from 'vue';

export default Vue.component('async-a', function(resolve, reject) {
    require(['./A'], (A) => {
        resolve(A.default);  // how to pass props to A??
    });
});

// A.js
import Vue from 'vue';

export default Vue.extend({
    template: `msg: ${msg}`,
    props: ['msg']
});

// App.js
import Vue from 'vue';
import AsyncA from './asyncA';
new Vue({
    el: '#app',
    components: {
        'async-a': AsyncA
    },
    template: '<async-a msg="msg"></async-a>',
    data() {
         return { msg: "come from app"}
    }
});

As the code above showed, I can pass props to async-a, but the 'real' component A will not get msg prop.
My question is similar to http://stackoverflow.com/questions/38344091/vuejs-can-we-give-props-to-async-component-via-dynamic-component-pattern-compo, but the accepted answer doesn't look like a best way.

You are using es6 string interpolation for the template, which inserts the value immediately when defining the component. Instead you should use Vue template syntax:

template: 'msg: {{msg}}'

You forgot to bind the msg:

<async-a :msg="msg"></async-a>

Closing, because this was a usage question, and we encourage you to ask questions on forum or gitter. The issue tracker is reserved for bug reports and feature requests.

authors: maple-leaf simplesmiler


text:
Question

Version
2.4.4
Reproduction link
https://jsfiddle.net/vmh5xm6z/
Async components can not be instantiated programmatically and manually mounted in the DOM
Steps to reproduce
When I try to manually create an instance of the async component I must provide a resolve function in the constructor for the component to work. However I can not find any method that is exposed in Vue.js to do that
What is expected?
the return constructor function after component registration should have the correct resolver inside supplied by Vue
What is actually happening?
Vue.component just returns the function supplied in the component registration

That's expected behavior. How do you instantiate something that isn't even resolved yet?

Yes, I want to instantiate a component that is not resolved yet.
I think this is more of a feature suggestion  :). It would be nice if async components can be used the same way as the normal ones.
Currently I can not find any way that Vue exposes to manually resolve the component.


text:
[Proposal] Content linting

Hi there!
In the VuePress documentation, we've set up content and Markdown linting with textlint and remark-lint. This is helpful to ensure consistency over natural language style, Markdown formatting, and help to enforce rules that have been decided upon.
Similarly to ESLint, textlint lets you add and configure rules as plugins, and create your own. These can be checked in the CI or as a pre-commit hook and allow reviewers to focus on meaning instead of style.
Examples of rules that we've activated in VuePress:

textlint-rule-apostrophe, to use consistent apostrophes (instead of a mix of straight and curly)
textlint-rule-common-misspellings, to catch common typos from this curated list
textlint-rule-terminology, to consistently spell terms, brands and technologies spelling (no more "npm" and "NPM" across docs!)
textlint-rule-write-good, to improve English prose and make the Vue docs even more enjoyable to read (if such a thing is even possible)

Here's a more exhaustive list: https://github.com/textlint/textlint/wiki/Collection-of-textlint-rule
If this is something that interests you, I'm willing to take care of setting it up, install and configure the rules that you want to activate, and start the process of running it through the documentation.
Let me know what you think!

As we're moving to VuePress for Vue 3 docs, we set up rules there 👍
If you're willing to work on Vue 2 documentation linting, please do so but my concern is it might be wasting your time and effort

@NataliaTepluhina Great news! Indeed, if this is happening on the Vue 3 docs, it's probably overkill to add it on the Vue 2 docs which will lose viewership with time anyway.
Thanks for your prompt reply! I'm closing this then 🙂

@sarahdayan as soon as we open Vue 3 docs  - would you mind helping us with linters? 😅

@NataliaTepluhina Of course, I would love to!

authors: NataliaTepluhina sarahdayan


text:
updated nuxt & vuetify to latest and fixed eslint error (no more eslint error)

Updated all dependencies & devDependencies to latest
I Personally tested it without a-la-carte and it works well, also i tested with a-la-carte and it works well but i did some changes in the code, here i will show you two demos check it it works fine with new updated code with nuxt generate / nuxt build, for a-la-carte i need to some tests more and i need some helps too,
for a-la-carte i used vuetify-loader and followed its docs works great without any eslint errors
demo sites
Normal Vuetify Nuxt template ( without a-la-carte )
https://nuxt-test-vuetify.herokuapp.com/
with a-la-carte
https://nuxt-vuetify-a-la-carte-test.herokuapp.com/
to test my repository by adding this command
$ vue init Codefa/nuxt my-project

Your PR covers my previous PR + more so I closed it in favor of this.

Your PR covers my previous PR + more so I closed it in favor of this.

@XanderLuciano can you test my repoitory please select A la carte and tet A la carte works or not i'm not sure about that please check it https://github.com/Codefa/nuxt
$vue init Codefa/nuxt appname

authors: Codefa XanderLuciano

repo: vuetifyjs/nuxt


text:
docs: add plugins page

Add plugins page to the docs.
Type of PR:

[ ] Bugfix
[ ] Feature
[ ] Refactor
[ ] Code style update
[ ] Build-related changes
[ ] Test
[x] Documentation
[ ] Other, please describe:

Nice! Thanks 👍

repo: vuex-orm/vuex-orm-next


text:
Proc macro panic

Not exactly sure what this message means that I am getting with the new proc macro stuff.
Not possible to generate a rust array with the correct alignment since the SPIR-V ArrayStride is larger than the size of the array element in rust. Try wrapping the array element in a struct or rounding up the size of a vector or matrix (e.g. increase a vec3 to a vec4)
layout(location = 0) out vec4 out_color;

layout(set = 0, binding = 0) uniform sampler2D color_tex;
layout(set = 0, binding = 1) uniform sampler2D normal_tex;
layout(set = 0, binding = 2) uniform sampler2D depth_tex;
layout(set = 0, binding = 3) uniform sampler2D trans_color_tex;
layout(set = 0, binding = 4) uniform sampler2D trans_normal_tex;
layout(set = 0, binding = 5) uniform sampler2D trans_depth_tex;
layout(set = 0, binding = 6) uniform sampler2D shadow_tex;
layout(set = 0, binding = 7) uniform samplerCube sky_box;

layout(set = 0, binding = 8) uniform Data {
	vec3 samples[512];
} uni;

layout(set = 1, binding = 0) uniform Other {
	int win_size_x;
	int win_size_y;
	float aspect_ratio;
	mat4 view;
	mat4 inverse_view;
	mat4 projection;
	mat4 inverse_projection;
	mat4 shadow_vp;
	int shadow_state;
	vec3 sun_direction;
	int samples;
	float strength;
	float sample_scale;
	float range;
} other;

Yeah, that will be from this commit https://github.com/vulkano-rs/vulkano/commit/7fea44b4da3e2f968ec9b547039e40b612e85953

I think you can resolve the issue by changing the vec3 to a vec4 (the 4th element will just be a dummy)

Thanks for the quick help!

repo: vulkano-rs/vulkano


text:
Allow copy_image, blit_image and copy_buffer source and destination to be the same image

This PR added a fix to allow copy_image, blit_image and copy_buffer to work with src and dest images/beffers being the same.
The doc: srcImage and dstImage can be the same image or alias the same memory.
This was achieved by locking only one image exclusively if both are the same. And in order for this to work safely, we need to add checks for overlapping regions, since regions cannot overlap in memory in any of the above mentioned commands.
Entries for Vulkano changelog:
- Allowed `copy_image`, `blit_image` and `copy_buffer` to work with `src` and `dest` images/beffers being the same.
But, regions from src to dest must not overlap.

I also made an example, a copy from image with some edits

Nice fix! Can you make this work for buffer self-copies too? And image blits maybe?

Yes sure

I noticed in the docs, that in these commands, while its allowed to have the same buffer for src and dest, regions must not overlap. I'll work on adding some checks to make sure the regions are not overlapping.

Now the implementation is complete, and is safe. I'll edit the example to include the other functions to showcase them.

I think this is now ready for review.

Not related to your PR directly, but I wonder if there's a neat way to demonstrate things without making a full Rust program for each one.

Yes, I was thinking of similar thing. An idea is to make a nice flow for unit tests, we can create a mock device and try to replicate some gpu functionality on the cpu. if we got this working or something similar, we can do better unit tests (to handle all vulkan documentation) and we can use doctests easily.

@Amjad50 Thank you very much for your work! The code looks good and all examples work as expected. No regressions detected. PR merged :+1:

authors: Amjad50 Eliah-Lakhin Rua


text:
Backup mnemonic flow

This PR fixes PR#164 and updates the flow according to new changes merged on master.
it closes #164
it closes #125
@tiero @Janaka-Steph please review

LGTM
Why the fixtures are being removed?

LGTM
Why the fixtures are being removed?

Not used since the redux refacto, let's revert later if we need them

authors: Janaka-Steph louisinger

repo: vulpemventures/marina


text:
[BUG] Rename screen , show existing vault's name

Describe the bug

When user get into "Rename vault screen , please display existing vault's name here

closing , fixed

repo: vultisig/vultisig-windows


text:
Errors on UseRef$1 and Invariant Violation

Hi there, first of all, thank you for building out this library as it will be a great help!
I'm basically copying your Example component and trying to see if it works on my app. I'm getting these errors and the component does not show up at all. Just wondering if I don't have the right requirements to use this.
I'm on React version 15.5.4. Not sure if that matters. What am I doing wrong?

hi @veinhuang , your react version is out of date, not include hook API used in the component. You should update to v16.8 or upper.

oh, I didn't know this required a certain React version.
Unfortunately, the app that my company app is on is a pretty big one and has been working on it for a few years so upgrading is not so easy (lots of breaking changes if React is upgraded). Would you happen to know another package that has similar functionality like yours?

Sorry for lately reply. I have not seen any image uploading component function likely so I made one. You can try with some other popular components on Npm. Good luck.


text:
Long string for name

Let's discuss how we can tackle that problem.

We could also cut off names... but why does he have his job title in his name?

It's not the job title. It seems that is the academic degree.

Similar issue regarding cut off User data, see https://github.com/vutuv/vutuv/issues/435

authors: MichaelBiermann balticer cjfreeze wintermeyer

repo: vutuv/vutuv


text:
Nuget package is not signed (no strong name key file applied to DLL)

The nugget published DLL's should have a strong name.
Unable to compile with projects that are signed. Therefore you should sign your DLL so they can be references in other projects that are signed with a strong name / key.

@tebjan  Seems like the newest Nuget Package v2.0 is not signed :-(

authors: erdmenchen xantari

repo: vvvv/SVG

license: MS-PL


text:
re-write

hi vysec, i saw your code come up on my twitter feed and had been recently thinking of writing a similar tool so thought i would give yours a look.  however i was unable to get your code working quickly and have now almost entirely re-written it.  Its possible i was missing something obvious with your code but i thought i would give you sight of mine in case you a curious.

I gotta say, that's pretty legendary. :D

It's good code. I'm willing to accept as a PR. Though the recursion needs some help, it can end up with prompting you forever with issues. Also, it's currently adding the "non-accepted" organizations and domains to the final output.
If you're checking all the domains manually there's like 100s, then it can take you ages. I left -E -C flags on but the -D is intolerable.

Also, doesn't seem to write to disk? :P

Even when I click no, it still puts the organization name into "organisations" :S

@vysec i did not realise that you wanted the orgs/domains/email etc removed from the output i thought you just wanted them excluded from the recursive search.  I have updated to remove them from the output.  have also added writing of the file
As to the issues with recursion are you able to send something that can recreate it?  however keep in mind i only have a free api account on whoxy.

Eg. IF the organisation becomes something like "WHOIS COMPANY", then it does a reverse on WHOIS domain. etc... or there's "COMPANY 1", "COMPANY 2" .. "COMPANY 500", don't really wanna click through them all. But so far with my testing, it works OK :D
I tried to remove the non accepted emails and organizations and domains out of the code, but doesn't seem to work :S

If you can sort that out for me, I've got some minor changes then I think we can get this pulled, we should also add some credits to you for massively helping out refactoring (I know I'm bad at coding :D) and push it to version 1.1.

@vysec have you pulled in my most recent changes specifically with theses bits https://github.com/vysec/DomLink/pull/6/files#diff-c14827df5c8fb20738af4e8c9baa186fR196.
As to recursion i don't think it will get in a stuck loop however its definitely possible that you may be prompted a lot for some things.  there are a few ways to make that a bit easier.

normalise the company name e.g. lower case it and strip some chars
add a filter for company names,  emails, domains which should automatically get blacklisted

Well, there's a conflict and Idk how to use git properly, so I ended up merging it somehow or another. Let me fill in some credits for you then close this off.

enjoy and dont worry to much about the credits it shows up in the git log regardless.  have fun hacking ;)

repo: vysec/DomLink


text:
Update accepted_grant_applications.md

Update Nolik from Chainify

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant keeganquigley


text:
Add color to console in action response

green when sucess, red when fail

Tried quickly with chalk, didn't worked in windows terminal.

repo: wOvalle/cloudman-cli


text:
Support for Lightning Testing Service

For using Lightning Testing Service projects need to expand the assigned buildpacks with Java, Chrome and chromedriver.
LTS has the dependency that it then still needs to reference the chromedriver binaries using env variables as described at the bottom of this readme.
  "buildpacks": [
    {
      "url": "https://github.com/wadewegner/salesforce-cli-buildpack#v3"
    },
    {
      "url": "https://github.com/wadewegner/salesforce-dx-buildpack#v4-dev"
    },
    {
      "url": "https://github.com/heroku/heroku-buildpack-jvm-common"
    }
    {
      "url": "https://github.com/heroku/heroku-buildpack-google-chrome"
    },
    {
      "url": "https://github.com/heroku/heroku-buildpack-chromedriver"
    }
  ]

Resolved by using specific LTS config file.
{
  "drivers": {
    "chrome": {
      "version": 2.33,
      "arch": "x64",
      "baseURL": "https://chromedriver.storage.googleapis.com"
    }
  },
  "webdriverio": {
    "desiredCapabilities": {
      "browserName": "chrome",
      "chromeOptions": {
        "binary": "/app/.apt/usr/bin/google-chrome",
        "args": ["--headless"]
      }
    }
  }
}

repo: wadewegner/salesforce-dx-buildpack


text:
🛑 Wagestream UK Public Website is down

In faf317b, Wagestream UK Public Website (https://wagestream.com/en/) was down:

HTTP code: 429
Response time: 136 ms

Resolved: Wagestream UK Public Website is back up in ce596e7 after 7 minutes.

repo: wagestream/statuspage


text:
fix: parse Abi with zod as readonly array

Description
This PR sets the zod Abi schema from abitype/zod as readonly [] to match the Abi type declared in abitype.
Additional Information

[X] I read the contributing guide
[X] I added documentation related to the changes made.
[X] I added or updated tests related to the changes made.

Your ENS/address: windyy.eth

PR-Codex overview
Focus of the PR:
This PR focuses on making changes to the Abi parsing in the code, using zod as a readonly array.
Detailed summary:

Parse Abi with zod as a readonly array.
Replace code below to z.switch (https://github.com/colinhacks/zod/issues/2106).
Redefine AbiFunction | AbiConstructor | AbiFallback | AbiReceive since z.discriminate doesn't support z.preprocess on options (https://github.com/colinhacks/zod/issues/1490).
Calculate stateMutability for deprecated fields: constant and payable.
Update types and optional fields.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Sure, I will take a look soon.

repo: wagmi-dev/abitype


text:
Supporting proxy models throughout Wagtail

Issue Summary
While there are a number of issues/PRs relating to support of proxy models in various parts of Wagtail (#1736, wagtail/wagtail-modeladmin#16, wagtail/wagtail#1029, wagtail/wagtail#4273, wagtail/wagtail#3594), I feel that we're missing a trick by only looking at the those issues in isolation. This issue aims to discuss the matter more generally, with an aim to establishing a clean, consistent approach that can be applied throughout the wider project.
Where are we now?
There are a good few places in Wagtail where using proxy models fails to work as expected. The exact details vary from place to place, but I feel they can all really be summarised as follows:

Django creates Permission objects for each proxy model, but they are associated with the ContentType for the concrete model.
When we want to identify the ContentType for a model, we tend to use ContentType.objects.get_for_model() which, when provided with a proxy model, returns the ContentType for the concrete model by default.
ContentType.objects.get_for_model() supports a for_concrete_model option (which has a default value of True), which can be used to retrieve a unique ContentType object for each proxy model instead of that of the concrete model. But, Permission objects for the proxy models remain associated with the ContentType of the concrete model.
Because of all of the above, identifying the correct ContentType and Permission objects for a proxy model (or worse, identifying the relevant model from a Permission or ContentType object) becomes tricky.

Where do we want to be?
I think we can all agree that supporting proxy models is much simpler/cleaner when proxy models have their own ContentType, and model permissions are related to that ContentType. In fact, this is how Django intends for things to be from version 2.2
There's a clear desire for proxy model support in Wagtail, and the changes in Django 2.2 will make that easier, but changing our code to benefit from those changes would leave a gap in proxy model support in earlier Django versions, which would be nice to fill somehow.
We want using proxy models in Wagtail to be simple for developers, but we don't want to force wholesale data changes on to every project where Wagtail is installed, so there should at least be an 'opt-in' step.
How might we get there?
Below are the most up-to-date recommendations:

Update Wagtail to use for_concrete_model=False and for_concrete_models=False options throughout, wherever ContentType.objects.get_for_model() or ContentType.objects.get_for_models() are used (respectively).
For Django versions < 2.2, we utilise Django's post_migrate signal to update proxy model permissions to be associated with their respective ContentType objects, making things consistent accross all supported Django versions.
The functionality in step 2 would be disabled by default, so as not to force the Permission changes onto projects that utilise proxy models outside of Wagtail, and might not be planning to update to Django 2.2 anytime soon. Developers would opt-in by adding something like WAGTAIL_UPDATE_PROXY_MODEL_PERMISSIONS = True to their project's Django settings.
To make the changes reversible in Django < 2.2, a management command could be added, that would essentially do the opposite of the signal handler in step 2.

As always, looking forward to hearing other's thoughts/suggestions on this :)

@ababic thank you for the detailed writeup.
How much will https://github.com/django/django/pull/10381 buy us here? That PR looks like it has been slowly making its way through review (there's an open request for feedback on django-developers). It adds ContentType support for proxy models, and appears to include a migration that updates existing permissions to properly refer to proxy models.
Granted, if and when this is merged into Django (best case scenario might be 2.3), and Wagtail started relying on it, it'd mean inconsistent behavior for developers using older Django versions. Still, that inconsistency might be worth it if we could avoid having to duplicate some of that logic here.

@chosak it looks like the migration in that PR would remove the need for developers to run a separate script/management command to set up the ContentType and Permission objects, which is good.
Part 2 would also be redundant after those changes, since we would no longer have to worry about non-existent ContentType objects being created by ContentType.objects.get_for_model() - though, we would need to update all usages of that method to use for_concrete_model=False, for the new types to be picked up. But, if we're going to support earlier versions of Django in the same release (highly likely), we will need that too.

@chosak Thinking on this some more, I think we could combine the ContentType / Permission creation logic and the "getting a content type without accidentally creating one" into a single method. This would:

Make the overall solution more centralised (easier to review, maintain, and eventually remove)
Simplify the process for developers (we would no longer need to provide separate instructions for different Django versions).
Only create/modify ContentType and Permission objects for proxy models registered with Wagtail (we'll let Django force that globally when they are ready to).

I'm a bit late to the party, but if Django 2.2 solves a big chunk of the problem, I think it would be reasonable to say "you need to use Django 2.2+ to benefit from those changes as well", instead of trying to hack/bend Wagtail so it works with previous versions on Django as well (especially if we need to make sure to always use for_concrete_model which will be forgotten at some point and create bugs).
That being said, I don't know whether it would be easier for Wagtail to support Django newest additions while still being compatible with previous Django version or do what you are trying to accomplish here.

Thanks @loicteixeira.

Django 2.2 solves a big chunk of the problem, I think it would be reasonable to say "you need to use Django 2.2+ to benefit from those changes as well", instead of trying to hack/bend Wagtail

I can totally see why messing with permissions after every migration in Django migration < 2.2 is undesirable. Instead of integrating this into the codebase (where we'd have to test and maintain it), how would you feel about just providing this part as a code snippet in the docs or something?

especially if we need to make sure to always use for_concrete_model which will be forgotten at some point and create bugs

We can take two approaches here:

Update everywhere to for_concrete_model=False regardless of Django version and deal with the fallout.
Implement our own util/wrapper methods that conditionally add for_concrete_model=False in Django > 2.2.

With 1, I don't think we'd actually suffer any, because wherever we could support proxy models (pages, snippets, modeladmin), we don't. I agree the Django API is a little confusing here, but it IS the Django API - it would at least be clear what the code is doing.
2 is safer. Would make for more readable code throughout Wagtail. It might also put us in a better position to update Wagtail if the Django API changes here in the near future. But, it is obfuscation.

I might also add that the first approach is advantageous, because just using for_concrete_model=False would allow Wagtail to support proxy Page type models in < Django 2.2. This is because we override the permission model for pages, so it's not necessary for the Permission objects created by Django to be associated with the proxy model's content type. The Permission association thing is only really an issue in places where we do things with permissions (e.g. in group edit/modeladmin/snippet/ views)

@chosak @loicteixeira. I figured adding support for proxy Page models would be a good place to start here, as permissions aren't an issue there (Wagtail implements it's own tree-based permission model for pages, and so never cares about the ones associated with a model's ContentType).
The PR also adds some documentation to give an indication of proxy model support in Wagtail, and also introduces a couple of util methods we can build upon to expand support to non-page models.
See #5202

@ababic I appreciate all the effort that you have put into this feature.  I don't currently have a use for the Page proxy model functionality, but I really do need to have regular proxy models show correctly in the Django admin.  This StOfw issue was useful, but as you can see from my comment (and I know you're aware of this), it only partially solved the problem.

Hi @DanAtShenTech,
Thanks. Yes, these issues are definitely known to me, and I'm planning to fix them soon after #5202 has been merged.
There's currently no way to manage proxy model permissions via the Wagtail admin UI, even if all the correct model permissions have been registered via the correct hooks. The form/view needs updating to surface all models instead of just concrete ones. Even with these changes, it's only going to be possible to manage permissions for each individual proxy model in Django 2.2+. I still haven't figured out what to do for earlier versions of Django. One option is to only allow permissions to be configurable for the concrete model, and have those permissions filter down to all proxy models.

@ababic I just finished updating a project that uses several proxy models to Wagtail 2.5/Django 2.2.  This  StOflw answer contains a brief summary.
A thought:  The Django migration to update existing proxy model permissions to the new permissions system was only able to be written because the model name (either concrete or proxy) is at the end of the codename in auth_group_permissions.  You mentioned above that Wagtail uses its own permissions system for Page models and so does not rely solely on Django's permissions.  If you wanted to support Django <2.2, perhaps you could implement a permissions system for non-Page models that also does not rely solely on Django's permissions.  It seems like you could use the latter part of the codename to accomplish this.  You would, in effect, be doing, on-the-fly, what that Django 2.2 proxy model migration does one time.  I don't know, however, whether the <2.2 permissions structure pre-dates the release of Wagtail.  I suspect that it does because proxy model support has been around since at least Django 1.5.  But maybe the level of interest in proxy model support in Wagtail prior to 2.5 doesn't even warrant the effort required to accommodate it.
In any event, I think that correct proxy model support is such a compelling feature that it shouldn't be held up trying to do something with Django <2.2.  I think that appropriate notes in the documentation (at least in the ModelAdmin Customisation Primer) would be fine.  As I said in my StOflw answer, at least now I have full capability to have proxy models appear correctly (for the correct users) in the left side of the Wagtail admin.  Being able to set the permissions in the Wagtail admin would just be icing on the cake.

@ababic I just finished updating a project that uses several proxy models to Wagtail 2.5/Django 2.2.  Here is a brief StOflw answer about this experience.
Two thoughts in regard to supporting <2.2:

You stated above that the permissions system for Page models is something other than Django's permissions system.  I was wondering if you could implement an other-than-Django permissions system for non-Page models.  The single Django migration in 2.2 that migrates existing permissions for proxy models is only even possible because the latter part of the codename field is always the model name (either concrete or proxy).  If you would use this model name to look up permissions, it seems like you could create an on-the-fly permissions system that emulates what Django 2.2 now finally does through proper database table entries for concrete and proxy models.
I wonder if there is enough demand for proxy model support in Wagtail < 2.5 to warrant the effort.  I think that this feature is compelling enough that it could be done without concern about <2.5 (with appropriate notes made in the docs here and perhaps other places).

Hi @DanAtShenTech. Thanks for the input. In answer to a few of your points:

But maybe the level of interest in proxy model support in Wagtail prior to 2.5 doesn't even warrant the effort required to accommodate it.

Indeed :) When you account for all of additional machinery needed to store, retrieve and check permissions throughout, it adds up to a lot of work and ongoing maintenance. Doing this soley to support proxy models in earlier versions of django (which we probably won't even be supporting in another couple of years) would likely introduce more problems than it solves.
We'll go for full support with Django >2.2 first of all, then see how we go from there. My intention is to centralise the logic that identifies model permissions, which should put us in a better place to do something about earlier Django versions.

I think that appropriate notes in the documentation (at least in the ModelAdmin Customisation Primer) would be fine.

Yes, #5202 adds something to explain the general state of support. But I imagine a few notes in the relevant parts of the docs will also be useful if support is conditional based on Django version.

OK @ababic, so within the last couple of days I've been assigning user rights in the project referenced above which was updated to Wagtail 2.5/Django 2.2.  I was stunned to see all proxy models appear in the Wagtail admin Groups page ready for permissions assignment along with all other regular Django models.  I've assigned permissions and tried the different corresponding logins assigned to different groups, and all works as it should.  Does this surprise you too, or is this what you expected?

@DanielSwain that is kind of surprising. I thought the form itself only surfaces permissions for concrete models. But I must say, I have been rather a lot more focussed on the page model side of things for a while. I would hazard a guess that things are only working because your models are registered with modeladmin? I'd expect things might be different if you registered those models as snippets instead. It's these kind of inconsistencies that I think need resolving.

Yes @ababic, these proxy models are all registered with ModelAdmin in wagtailhooks.py.

It's possible I forgot to migrate when I tested things before, which would explain things not showing ul in the form :( I'll have another go locally and update the info #5202 accordingly.

@DanielSwain could you give #9255 a try? that is the latest and most up-to-date work on this.

To get correct permissions when accessing models through SnippetViewSet, you can use this hook
from django.contrib.auth.models import Permission
from django.contrib.contenttypes.models import ContentType
from .models import MyModel

@hooks.register("register_permissions")
def register_ctf_permissions():
    model = MyModel
    content_type = ContentType.objects.get_for_model(model, for_concrete_model=False)
    return Permission.objects.filter(content_type=content_type)

authors: AndersFelde DanAtShenTech DanielSwain ababic chosak loicteixeira zerolab

repo: wagtail/wagtail


text:
Feature request: select list or autocomplete when prompted for parent page

Issue Summary
I have a custom content model inheriting from Page, and have created a custom Admin page:

When clicking the "Add Contact" button, I am prompted to select a parent page:

Since we expect to have dozens or hundreds of contacts, this list grow to be too long for a radio-select.
How can I configure this page to use an autocomplete or page select widget?
Steps to Reproduce

create model inheriting from Page, allowing model to be child of self
create Admin page for model
add several instances of model
visit custom admin page and click "Create " button

You might want to have a look at Customising ChooseParentView. Please note though that support questions are better answered on Stack Overflow or Slack, see the Support page in the documentation. If you have further questions, please do not reply to this issue and use those channels linked.
I'll keep that issue open though because I think it could be addressed with better UI. Most of website will end up with a good number of pages which will make the radio buttons unusable.

I'll keep that issue open though because I think it could be addressed with better UI. Most of website will end up with a good number of pages which will make the radio buttons unusable.

Jep, there is a fine line between a support and feature request. Agreed that this would be a good core feature enhancement :-)

We're running into the same problem right now. It's not only that the user experience is bad; we have so many pages that the page load times out.
I will have a look at customizing the ChooseParentView with wagtail-autocomplete.

authors: brylie jnns loicteixeira


text:
Ensure redirect middleware preserves query strings

This PR intends to resolve an issue (https://github.com/wagtail/wagtail/issues/4414) where Wagtail's RedirectMiddleware does not preserve querystring parameters. I believe that querystrings should be preserved on redirect.
Tests and linting pass locally.
My only concern with this PR is that prior authors of the redirect middleware were aware of the behaviour that I'm trying to fix.
Looking at this relevant past issue (https://github.com/wagtail/wagtail/issues/647), I believe that my change doesn't conflict with the intent of the established logic, which stripped the querystring parameters to ensure that we can match a redirect with no params. My change preserves that behaviour.
Acceptance Criteria

[ ] Querystring parameters stripped from request before matching
[ ] Querystring parameters passed through to the redirect target
[ ] If there are querystring parameters already specified in the redirect_link, then they override any params passed through in the original request

Eg. established behavior
old_path        /redirectme
redirect_link   /target?foo=1

request         /redirectme/
response        /target/?foo=1

My change intends to preserve this behaviour, but also handle this case
old_path        /redirectme
redirect_link   /target

request         /redirectme/?foo=1
response        /target/?foo=1

There's also this tricky corner case, where I default to the respecting the redirect_link
old_path        /redirectme
redirect_link   /target?foo=1

request         /redirectme/?foo=2
response        /target/?foo=1

Thanks for contributing this! I can't remember if there's a reason why we strip the query string other than helping it match more URLs and cleaning out crufty URL parameters.
The implementation as it stands looks good to me, just an open question about whether we should strip out URL parameters that we were expecting in the original URL.

Added a defensive check against a missing QUERYSTRING key in request.META, which happened to me in testing a little while back.

Just pushed some new changes. Turns out I couldn't do everything I said that I would do. Most of it, but not everything. I think/hope my tests make the expected behavior pretty clear.
Can do:
Pass through requested params
from        /previous-search-page
to          /new-search-page
visit       /previous-search-page?q=keyword
redirect    /new-search-page?q=keyword

Strip old params:
from        /index.php?page-id=5
to          /about-us
visit       /index.php?page-id=5
redirect    /about-us

Merge requested and specified params:
from        /index.php
to          /about-us?foo=1
visit       /index.php?utm_source=12
redirect    /about-us?utm_source=12&foo=1

Respect redirected params
from        /previous-search-page?q=keyword
to          /new-search-page?q=keyword
visit       /previous-search-page?q=keyword
redirect    /new-search-page?q=keyword

Can't do:
If you visit a URL that doesn't match the old_path querystring exactly, then we won't be able to find a redirect. Even if we could there are potential conflicts where 2 redirects could match 1 request. As such, we can't easily do this:
from        /index.php?page-id=5
to          /about-us/
visit       /index.php?page-id=5&utm_source=12
redirect    /about-us/?utm_source=12

Instead we have to 404, or look for a redirect that doesn't have a querystring.

Hi @MattSegal - just wondering what the reason is for closing this? This is still something we're keen to fix, and was on our backlog to be reviewed...

Hi @gasman I'm thought that this PR had fallen by the wayside, given this is on your to-do list I'll re-open.

Given merge conflicts with wagtail/contrib/redirects/middleware.py I don't want to keep this open

Hmm there is a proposed solution and now it's closed? We would need this one. There is no alternative?

authors: MattSegal gasman kaedroho steverowland