Add pylint

This is the first draft about adding pylint to this repository.
What has been done :

Add pylint in the requirements
Update cryptography
Add pylintrc using the one in meilisearch-python
Add a github action to test with pylint on push and pr
Format using autopep8
Fix most of the errors raised by pylint

This is what's left to be fixed :
************* Module tools.create_droplet
tools/create_droplet.py:11:0: C0103: Constant name "logger" doesn't conform to '(([A-Z_][A-Z0-9_]*)|(__.*__))$' pattern (invalid-name)
tools/create_droplet.py:14:97: W0621: Redefining name 'logger' from outer scope (line 11) (redefined-outer-name)
tools/create_droplet.py:18:11: W0703: Catching too general exception Exception (broad-except)
tools/create_droplet.py:43:75: W0621: Redefining name 'logger' from outer scope (line 11) (redefined-outer-name)
tools/create_droplet.py:43:0: R0914: Too many local variables (36/25) (too-many-locals)
tools/create_droplet.py:54:4: C0103: Variable name "DIGITALOCEAN_ACCESS_TOKEN" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:56:4: C0103: Variable name "CLOUDFLARE_API_KEY" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:57:4: C0103: Variable name "CLOUDFLARE_EMAIL" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:58:4: C0103: Variable name "CLOUDFLARE_ZONE" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:62:4: C0103: Variable name "MEILI_VERSION" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:63:4: C0103: Variable name "MEILI_IMG_SLUG" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:68:4: C0103: Variable name "SIZE_SLUG" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:69:4: C0103: Variable name "DROPLET_NAME" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:70:4: C0103: Variable name "DROPLET_TAGS" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:71:4: C0103: Variable name "SSH_KEYS_FINGERPRINTS" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:75:4: C0103: Variable name "ENABLE_BACKUPS" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:85:4: C0103: Variable name "USE_API_KEY" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:86:4: C0103: Variable name "MEILISEARCH_API_KEY" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:87:4: C0103: Variable name "USE_SSL" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:88:4: C0103: Variable name "USE_CERTBOT" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:89:4: C0103: Variable name "DOMAIN_NAME" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:124:4: C0103: Variable name "USER_DATA" doesn't conform to '[a-z_][a-z0-9_]{2,30}$' pattern (invalid-name)
tools/create_droplet.py:159:16: E1101: Instance of 'CloudFlare' has no 'zones' member (no-member)
************* Module tools.do_meili_tools
tools/do_meili_tools.py:23:15: W0703: Catching too general exception Exception (broad-except)
tools/do_meili_tools.py:34:15: W0703: Catching too general exception Exception (broad-except)
tools/do_meili_tools.py:45:15: W0703: Catching too general exception Exception (broad-except)
tools/do_meili_tools.py:61:15: W0703: Catching too general exception Exception (broad-except)
************* Module tools.build_image
tools/build_image.py:74:4: C0103: Constant name "ssh_command" doesn't conform to '(([A-Z_][A-Z0-9_]*)|(__.*__))$' pattern (invalid-name)

------------------------------------------------------------------
Your code has been rated at 8.23/10 (previous run: 8.23/10, +0.00)

Closes #98

Is it possible to rename do_meili_tools.py to utils.py (and relink the modules) to have the same structure as in the other repos? :)

Yes, I'll do that 👍

Also, I don't know if we want to keep all the comments, doc, and unused values on .pylintrc. It feels quite polluted, but the information is quite useful for someone who is making modifications for contributors, etc... WDYT?

I believe we could clean it a bit, in order to make it readable and remove unused values, I'll do that when we are done configurating it (I'm thinking maybe number of locals for funtions and regex for constants/variables naming)

I will fix the last problems with pylint and push a commit on this same branch if you are OK with that 👌🏽

If you could that would be nice, as it will serve as an example (from the cloud scripts father) for me to do the same in the other repositories.
🎉🎉🎉

I almost forgot: we need to document that on the CONTRIBUTING.md. For this, the best inspiration will probably be the meilisearch-python CONTRIBUTING

Hey @eskombro 😊
I updated this branch with a few modifications.

I renamed the  do_meili_tools.py to utils.py and fixed the modules
I added a config.py that will contain all the constants for the build_image.py (as in the other cloud repos)
I updated the CONTRIBUTING.md, adding a Development Workflow and the linter commandes. I also changed a bit the release process as the files name changed.

I had an issue testing the build_image process, following the contributing.md and release steps :
On step # Execute deploy script via SSH in the python script, I had some permission denied, which resulted in the commands not being applied but the snapshot being created. I added this issue in #145.
I suspected it might come from the SSH_KEYS_FINGERPRINTS not being updated for me?
So I changed those with my public key, and then it would run smoothly except for one thing, I have one test that doen't pass in the img_check.sh script from digitalocean. You'll find the output below. Maybe the script applied after fixed that (cleanup.sh), but please confirm. Also if that's the case, might be a good idea to change the order 😁
[PASS] User meilisearch has no password set.
[ OK ] User meilisearch has no SSH keys present
Checking the root account...
[PASS] User root has no password set.
[FAIL] User root has a populated authorized_keys file in /root/.ssh/authorized_keys
File Contents:
ssh-rsa <my publickey>
--------------
[PASS] The Root User's Bash History is not present
[PASS] DigitalOcean Monitoring agent was not found
[PASS] MongoDB is not installed
---------------------------------------------------------------------------------------------------
Scan Complete.
One or more tests failed.  Please review these items and re-test.
---------------------------------------------------------------------------------------------------
9 Tests PASSED
0 WARNINGS
1 Tests FAILED
---------------------------------------------------------------------------------------------------
Some critical tests failed.  These items must be resolved and this scan re-run before you submit your image to the DigitalOcean Marketplace.```

About the no-member errors raised by pylint, there is options to put in the pylintrc file :
generated-members or ignored-module
See https://docs.pylint.org/en/1.6.0/features.html

About the no-member errors raised by pylint, there is options to put in the pylintrc file :
generated-members or ignored-module
See https://docs.pylint.org/en/1.6.0/features.html

Instead of disabling the rule, I just added an exception to this specific class, since this attribute is apparently created dynamically
I also disabled the check for W0703: Catching too general exception Exception (broad-except). These are indeed intentionally broad excepts because trying to catch every specific exception that could come up in the image build is not necessary. These try/except are just there to avoid problems trying to reach the machine while it is being created or unavailable (health check on a machine while it is being created for example, which could raise an Exception) inside the wait_for... methods.

The order in which these scripts are executed (img_check.sh and cleanup.sh) can not just be changed: the cleanup.sh script will remove your SSH key! So this has to be the last command. If you try to run the img_check.sh afterward via SSH, this will fail. So as for now, having 1 fail on the img_check.sh corresponding to the SSH key present for the root user is OK, since right after this we are doing the cleanup. If you have another idea on how to run it, we can of course discuss it. :)

This makes sense, and yes you're right we can't reverse them. It's just a bit annoying to me that we can't use this test as a final checker, stopping the process if we get an error for example. We still have to read the output to know if there might be another error than the ssh key. Anyway, this is far from the pylint scope, let me know if you think we should add it as a potential issue. I think that there is a few places where the script should stop and not create the snapshot.


Potential naming enhancements for classes and entities

In this issue, we'll try to improve some of the naming conventions used to name classes, entities or database tables, in order to make them more significant and descriptive.

@tcezard
Should we keep this issue open, because I think we're making the enhancements on the way.


Rename the oorset_ps as the awset_ps

It looks like Travis CI is continuously timed out.

That's a known problem, you can ignore it.


GUI file open dialog: Last file in list not readable

From Adrian:
GUI File Open Dialog Letzte Datei in Liste nicht lesbar
From @devhoffmann:
This seems to only happen on macOS (MUHAHAHAHAHA)

Will be fixed in 707c83e


Is launch by URL still used?

I'm converting the App Delegate to Swift as there isn't much in it and there are a couple of things that need to be added to the App Delegate for the shortcuts stuff.
While converting, there was something I noticed here:
https://github.com/aaronpk/Overland-iOS/blob/f150bfcf87d8aec0b1d8a9cefb11c34ef7f18eb5/GPSLogger/AppDelegate.m#L63-L73
It seems that the app is set up for opening URLs but when I look at the actual project settings I don't see any URL schemes set up. Is this functionality actually used? I can put in the swift version but I don't know how to test it because I don't see an existing app url scheme.

I had configured a custom URL scheme to be able to launch the app and store an API endpoint from a URL. I was using this to quickly configure phones by sending a link via SMS. It's possible the custom URL scheme got lost at some point, but I'd like to restore the functionality.

👍 sounds good. What was the custom url scheme, overland:// ?

Oh I think this existed before it was called Overland, but yeah let's go wth that!

This is fixed, and the endpoint, access token and device ID can all be set from the custom URL scheme now.


Please help multi remote Windows 10 19044.1288

Dear
Please path help me file tearm Windows 10 19044.1288. Thanks so much
termsrv.zip

duplicate of https://github.com/stascorp/rdpwrap/issues/1509


fix(sender): nonce update

Purpose or design rationale of this PR
Only updating nonce when sending transaction success.
PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

[x] fix: A bug fix

Deployment tag versioning
Has tag in common/version.go been updated or have you added bump-version label to this PR?

[x] Yes

Breaking change label
Does this PR have the breaking-change label?

[x] No, this PR is not a breaking change

Summary by CodeRabbit

New Features

Updated version number to v4.4.82, reflecting the latest release.
Improved transaction sending logic to directly manage nonce, enhancing transaction reliability.

Bug Fixes

Enhanced error handling and logging for transaction creation and sending processes.

Tests

Updated tests to ensure correct nonce usage and transaction status tracking across various scenarios.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 52.03%. Comparing base (06beb5d) to head (99f9020).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1570      +/-   ##
===========================================
- Coverage    52.06%   52.03%   -0.04%
===========================================
  Files          157      157
  Lines        12472    12464       -8
===========================================
- Hits          6494     6486       -8
  Misses        5418     5418
  Partials       560      560

Flag
Coverage Δ

rollup
57.06% <100.00%> (-0.09%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


eBPF native routing is slow to learn service IP changes

Is there an existing issue for this?

[x] I have searched the existing issues

Version
equal or higher than v1.16.0 and lower than v1.17.0
What happened?
This issue occurs when using eBPF native host routing, but does not occur when using legacy kubeproxy mode.
When Portworx runs PVCs in v4Service mode, it creates a ClusterIP service for each NFS export. Each service points to the host IP for the NIC that Portworx is configured to use as the dataplane. If a node is shutdown, this host IP stops responding and Portworx orchestrates an NFS failover by updating the ClusterIP service to point to the host IP of a different node that also has a copy of the data.
When Cilium is running in legacy kubeproxy mode (or when using a different CNI altogether in kubeproxy mode), this NFS failover happens quickly and generally does not cause any disruption. However when Cilium is running in eBPF native routing (kubeproxy-free) mode, the failover is very slow, taking up to several minutes. This breaks the consumers of the NFS-based PVCs.
Since all that Portworx does is update the ClusterIP service to point to a different IP, there must be something in Cilium native routing that causes this change to take longer to learn. Is there some caching mechanism that cause such a change to take longer to learn? Can that be disabled?
The practical use case is Kubevirt VMs, where this NFS failover delay can take too long and crashes the VM with a disk I/O error.
We are forced to revert Cilium to legacy kubeproxy mode in order to be able to run Kubevirt with Portworx reliably.
How can we reproduce the issue?

Install Cilium in eBPF native routing mode
Install Portworx Enterprise in trial mode and set up a storage class for Kubevirt use
Install Kubevirt and make 20 VMs
Shut down a node and watch the VMs that were running off NFS-based PVCs from the shutdown node take a long time to failover and probably crash.

Cilium Version
1.16.3
Kernel Version
6.5.0-26-generic
(Ubuntu 22.04 LTS)
Kubernetes Version
1.30.5
Regression
No response
Sysdump
No response
Relevant log output
virt-launcher logs of a VM experiencing this long NFS failover delay, but eventually came back at 13:32:11
----------------------------------------------------------------------------------------------------------

{"component":"virt-launcher","level":"error","msg":"Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo)","pos":"virDomainObjBeginJobInternal:467","subcomponent":"libvirt","thread":"31","timestamp
{"component":"virt-launcher","level":"info","msg":"Received signal terminated","pos":"virt-launcher.go:473","timestamp":"2024-11-12T13:29:09.539050Z"}
{"component":"virt-launcher","kind":"VirtualMachineInstance","level":"info","msg":"Signaled graceful shutdown","name":"vm-filler-ubuntu-3","namespace":"default","pos":"virt-launcher.go:443","timestamp":"2024-11-12T13:29:09.539220Z","uid":"356d08cc-9e85-4b
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:29:09.831000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:29:14.834000Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Running(1):Unknown(2)","pos":"client.go:297","timestamp":"2024-11-12T13:29:14.839362Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to send domain notify event. closing connection.","pos":"client.go:218","reason":"rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial unix /var/run/
{"component":"virt-launcher","level":"info","msg":"failed to dial notify socket: /var/run/kubevirt/domain-notify-pipe.sock","pos":"client.go:149","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:17.840846Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to connect to notify server","pos":"client.go:209","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:17.840905Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:29:19.836000Z"}
{"component":"virt-launcher","level":"info","msg":"failed to dial notify socket: /var/run/kubevirt/domain-notify-pipe.sock","pos":"client.go:149","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:20.842211Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to connect to notify server","pos":"client.go:209","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:20.842275Z"}
{"component":"virt-launcher","level":"info","msg":"failed to dial notify socket: /var/run/kubevirt/domain-notify-pipe.sock","pos":"client.go:149","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:23.841542Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to connect to notify server","pos":"client.go:209","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:23.841619Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:29:24.839000Z"}
{"component":"virt-launcher","level":"info","msg":"failed to dial notify socket: /var/run/kubevirt/domain-notify-pipe.sock","pos":"client.go:149","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:26.841270Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to connect to notify server","pos":"client.go:209","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:26.841342Z"}
{"component":"virt-launcher","level":"warning","msg":"Cannot start job (none, modify, none) in API qemuDispatchDomainAgentCommand for domain default_vm-filler-ubuntu-3; current job is (query, modify, none) owned by (32 remoteDispatchDomainGetBlockInfo, 33
{"component":"virt-launcher","level":"error","msg":"Timed out during operation: cannot acquire state change lock (held by agent=qemuDispatchDomainAgentCommand)","pos":"virDomainObjBeginJobInternal:471","subcomponent":"libvirt","thread":"29","timestamp":"2
{"component":"virt-launcher","level":"info","msg":"failed to dial notify socket: /var/run/kubevirt/domain-notify-pipe.sock","pos":"client.go:149","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:29.841570Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to connect to notify server","pos":"client.go:209","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:29.841623Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:29:29.842000Z"}
{"component":"virt-launcher","level":"info","msg":"failed to dial notify socket: /var/run/kubevirt/domain-notify-pipe.sock","pos":"client.go:149","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:32.840977Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to connect to notify server","pos":"client.go:209","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:32.841046Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"29","timestamp":"2024-11-12T13:29:34.844000Z"}
{"component":"virt-launcher","level":"info","msg":"failed to dial notify socket: /var/run/kubevirt/domain-notify-pipe.sock","pos":"client.go:149","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:35.840618Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to connect to notify server","pos":"client.go:209","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:35.840681Z"}
{"component":"virt-launcher","level":"info","msg":"failed to dial notify socket: /var/run/kubevirt/domain-notify-pipe.sock","pos":"client.go:149","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:37.840933Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to connect to notify server","pos":"client.go:209","reason":"context deadline exceeded","timestamp":"2024-11-12T13:29:37.840996Z"}
{"component":"virt-launcher","level":"info","msg":"Failed to send domain notify event","pos":"client.go:228","reason":"timed out waiting for the condition","timestamp":"2024-11-12T13:29:37.841025Z"}
{"component":"virt-launcher","level":"error","msg":"Could not send domain notify event.","pos":"client.go:357","reason":"timed out waiting for the condition","timestamp":"2024-11-12T13:29:37.841079Z"}
{"component":"virt-launcher","level":"warning","msg":"Cannot start job (query, none, none) in API remoteDispatchConnectGetAllDomainStats for domain default_vm-filler-ubuntu-3; current job is (query, modify, none) owned by (32 remoteDispatchDomainGetBlockI
{"component":"virt-launcher","level":"error","msg":"Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo)","pos":"virDomainObjBeginJobInternal:467","subcomponent":"libvirt","thread":"31","timestamp
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:29:39.847000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"31","timestamp":"2024-11-12T13:29:44.850000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:29:49.853000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:29:54.855000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:29:59.862000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:30:04.869000Z"}
{"component":"virt-launcher","level":"warning","msg":"Cannot start job (query, none, none) in API remoteDispatchDomainMemoryStats for domain default_vm-filler-ubuntu-3; current job is (query, modify, none) owned by (32 remoteDispatchDomainGetBlockInfo, 31
{"component":"virt-launcher","level":"error","msg":"Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo)","pos":"virDomainObjBeginJobInternal:467","subcomponent":"libvirt","thread":"29","timestamp
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"31","timestamp":"2024-11-12T13:30:09.871000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:30:14.878000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:30:19.885000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:30:24.892000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:30:29.899000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:30:34.906000Z"}
{"component":"virt-launcher","level":"warning","msg":"Cannot start job (query, none, none) in API remoteDispatchConnectGetAllDomainStats for domain default_vm-filler-ubuntu-3; current job is (query, modify, none) owned by (32 remoteDispatchDomainGetBlockI
{"component":"virt-launcher","level":"error","msg":"Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo)","pos":"virDomainObjBeginJobInternal:467","subcomponent":"libvirt","thread":"29","timestamp
{"component":"virt-launcher","level":"warning","msg":"Cannot start job (none, modify, none) in API qemuDispatchDomainAgentCommand for domain default_vm-filler-ubuntu-3; current job is (query, modify, none) owned by (32 remoteDispatchDomainGetBlockInfo, 33
{"component":"virt-launcher","level":"error","msg":"Timed out during operation: cannot acquire state change lock (held by agent=qemuDispatchDomainAgentCommand)","pos":"virDomainObjBeginJobInternal:471","subcomponent":"libvirt","thread":"31","timestamp":"2
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:30:39.913000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:30:44.915000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"29","timestamp":"2024-11-12T13:30:49.922000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:30:54.929000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:30:59.936000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:31:04.943000Z"}
{"component":"virt-launcher","level":"warning","msg":"Cannot start job (query, none, none) in API remoteDispatchDomainMemoryStats for domain default_vm-filler-ubuntu-3; current job is (query, modify, none) owned by (32 remoteDispatchDomainGetBlockInfo, 30
{"component":"virt-launcher","level":"error","msg":"Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo)","pos":"virDomainObjBeginJobInternal:467","subcomponent":"libvirt","thread":"31","timestamp
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:31:09.950000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:31:14.957000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:31:19.964000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:31:24.966000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:31:29.974000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:31:34.980000Z"}
{"component":"virt-launcher","level":"warning","msg":"Cannot start job (query, none, none) in API remoteDispatchConnectGetAllDomainStats for domain default_vm-filler-ubuntu-3; current job is (query, modify, none) owned by (32 remoteDispatchDomainGetBlockI
{"component":"virt-launcher","level":"error","msg":"Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo)","pos":"virDomainObjBeginJobInternal:467","subcomponent":"libvirt","thread":"29","timestamp
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:31:39.982000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:31:44.984000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:31:49.987000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:31:54.989000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:31:59.991000Z"}
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"33","timestamp":"2024-11-12T13:32:04.993000Z"}
{"component":"virt-launcher","level":"warning","msg":"Cannot start job (query, none, none) in API remoteDispatchDomainMemoryStats for domain default_vm-filler-ubuntu-3; current job is (query, modify, none) owned by (32 remoteDispatchDomainGetBlockInfo, 30
{"component":"virt-launcher","level":"error","msg":"Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo)","pos":"virDomainObjBeginJobInternal:467","subcomponent":"libvirt","thread":"31","timestamp
{"component":"virt-launcher","level":"error","msg":"Guest agent is not responding: Guest agent not available for now","pos":"qemuAgentSend:754","subcomponent":"libvirt","thread":"30","timestamp":"2024-11-12T13:32:09.995000Z"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"vm-filler-ubuntu-3","namespace":"default","pos":"server.go:208","timestamp":"2024-11-12T13:32:11.734556Z","uid":"356d08cc-9e85-4b6c-94b3-df767a905d57"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"vm-filler-ubuntu-3","namespace":"default","pos":"server.go:208","timestamp":"2024-11-12T13:32:11.791175Z","uid":"356d08cc-9e85-4b6c-94b3-df767a905d57"}
{"component":"virt-launcher","kind":"","level":"info","msg":"Synced vmi","name":"vm-filler-ubuntu-3","namespace":"default","pos":"server.go:208","timestamp":"2024-11-12T13:32:11.800607Z","uid":"356d08cc-9e85-4b6c-94b3-df767a905d57"}
{"component":"virt-launcher","level":"info","msg":"Grace Period expired, shutting down.","pos":"monitor.go:194","timestamp":"2024-11-12T13:32:25.324957Z"}
{"component":"virt-launcher-monitor","level":"info","msg":"Reaped pid 76 with status 0","pos":"virt-launcher-monitor.go:198","timestamp":"2024-11-12T13:32:25.545800Z"}
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event Domain event=\"shutdown\" detail=\"unknown\" with event id 6 reason 2 received","pos":"client.go:470","timestamp":"2024-11-12T13:32:25.733274Z"}
{"component":"virt-launcher","kind":"VirtualMachineInstance","level":"info","msg":"Domain stopped.","name":"vm-filler-ubuntu-3","namespace":"default","pos":"manager.go:1847","timestamp":"2024-11-12T13:32:25.734628Z","uid":"356d08cc-9e85-4b6c-94b3-df767a90
{"component":"virt-launcher","level":"info","msg":"DomainLifecycle event Domain event=\"stopped\" detail=\"destroyed\" with event id 5 reason 1 received","pos":"client.go:470","timestamp":"2024-11-12T13:32:25.734788Z"}
{"component":"virt-launcher","level":"info","msg":"kubevirt domain status: Shutoff(5):Destroyed(2)","pos":"client.go:297","timestamp":"2024-11-12T13:32:25.737217Z"}
{"component":"virt-launcher","level":"info","msg":"Process default_vm-filler-ubuntu-3 and pid 76 is gone!","pos":"monitor.go:179","timestamp":"2024-11-12T13:32:26.324842Z"}
{"component":"virt-launcher","level":"info","msg":"Waiting on final notifications to be sent to virt-handler.","pos":"virt-launcher.go:281","timestamp":"2024-11-12T13:32:26.324868Z"}
{"component":"virt-launcher","level":"info","msg":"failed to dial notify socket: /var/run/kubevirt/domain-notify-pipe.sock","pos":"client.go:149","reason":"context deadline exceeded","timestamp":"2024-11-12T13:32:27.738605Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to connect to notify server","pos":"client.go:209","reason":"context deadline exceeded","timestamp":"2024-11-12T13:32:27.738671Z"}
{"component":"virt-launcher","level":"info","msg":"failed to dial notify socket: /var/run/kubevirt/domain-notify-pipe.sock","pos":"client.go:149","reason":"context deadline exceeded","timestamp":"2024-11-12T13:32:30.739017Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to connect to notify server","pos":"client.go:209","reason":"context deadline exceeded","timestamp":"2024-11-12T13:32:30.739096Z"}
{"component":"virt-launcher","level":"info","msg":"failed to dial notify socket: /var/run/kubevirt/domain-notify-pipe.sock","pos":"client.go:149","reason":"context deadline exceeded","timestamp":"2024-11-12T13:32:33.740328Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to connect to notify server","pos":"client.go:209","reason":"context deadline exceeded","timestamp":"2024-11-12T13:32:33.740400Z"}
{"component":"virt-launcher","level":"info","msg":"failed to dial notify socket: /var/run/kubevirt/domain-notify-pipe.sock","pos":"client.go:149","reason":"context deadline exceeded","timestamp":"2024-11-12T13:32:36.739973Z"}
{"component":"virt-launcher","level":"error","msg":"Failed to connect to notify server","pos":"client.go:209","reason":"context deadline exceeded","timestamp":"2024-11-12T13:32:36.740072Z"}

Anything else?
No response
Cilium Users Document

[x] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

[x] I agree to follow this project's Code of Conduct

Thanks for this issue @kreeuwijk. Could you please add a sysdump using the instructions at https://docs.cilium.io/en/stable/operations/troubleshooting/#automatic-log-state-collection ? That will enable whoever picks this up to have a quick look without needing to do a full reproduction.


fix: manage direction of hover when grid table smaller than grid

Hi! I have a use-case where the canvas is stretched over the whole screen but sometimes there are not enough rows/columns to fully fill the grid in all directions. The current behavior of the grid is to create an empty space which is classified as an out-of-bound cell with direction [0,0].
To be able to exactly pinpoint right / bottom / bottom-right, I would like to know the inner direction too based on the col and row.
I suggest doing it by adding a new field, innerDirection, to the GridMouseOutOfBoundsEventArgs payload, which in conjunction with the direction field, allows us to clearly identify the source of the mouse event.
In addition, I also would like to trigger the onItemHover function whenever the direction or the inner direction of my "out-of-bound" cell changes - which I also included as part of this PR.
Please let me know if you agree with this approach and the new names.
Thank you!

Can you give me a quick sample code of how you want to use this?

I think this makes a lot more sense, what do you think?

That is awesome! Thank you 😊 It makes more sense now


BootstrapDetectionError: Unable to detect CDK bootstrap stack due to permission issues. On backend build Unable to deploy monorepo.

Environment information
System:
  OS: macOS 15.1
  CPU: (11) arm64 Apple M3 Pro
  Memory: 111.02 MB / 18.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 22.11.0 - ~/Library/pnpm/node
  Yarn: undefined - undefined
  npm: 10.9.0 - ~/Library/pnpm/npm
  pnpm: 9.12.3 - ~/Library/pnpm/pnpm
NPM Packages:
  @aws-amplify/auth-construct: Not Found
  @aws-amplify/backend: 1.7.0
  @aws-amplify/backend-auth: Not Found
  @aws-amplify/backend-cli: 1.4.2
  @aws-amplify/backend-data: Not Found
  @aws-amplify/backend-deployer: Not Found
  @aws-amplify/backend-function: Not Found
  @aws-amplify/backend-output-schemas: Not Found
  @aws-amplify/backend-output-storage: Not Found
  @aws-amplify/backend-secret: Not Found
  @aws-amplify/backend-storage: Not Found
  @aws-amplify/cli-core: Not Found
  @aws-amplify/client-config: Not Found
  @aws-amplify/deployed-backend-client: Not Found
  @aws-amplify/form-generator: Not Found
  @aws-amplify/model-generator: Not Found
  @aws-amplify/platform-core: Not Found
  @aws-amplify/plugin-types: Not Found
  @aws-amplify/sandbox: Not Found
  @aws-amplify/schema-generator: Not Found
  aws-amplify: 6.8.0
  aws-cdk: 2.166.0
  aws-cdk-lib: 2.166.0
  typescript: 5.5.4
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Describe the bug
I've been trying to setup a custom repository for a monorepo that will have several apps hosted on it.
The objective is to be able to share the backend with multple web and mobile apps.
I cant seem to  be able to build the backend.
I get the following error within the console when attempting to build it.
BUILD.txt
this is the current repo
https://github.com/KinuQ/kinuqmono
Im honestly not sure what is it that I'm doing wrong.
I had another single repo app with a full fledged backend, and it is able to just go ahead and get deployed without an issue.
this is my amplify.yml for the CI process
version: 1
backend:
  phases:
    preBuild:
      commands:
        - corepack enable
        - pnpm install
    build:
      commands:
        - echo $AWS_BRANCH
        - echo $AWS_APP_ID
        - pwd
        - cd packages/amplify
        - pwd
        - pnpm exec ampx pipeline-deploy --branch $AWS_BRANCH --app-id $AWS_APP_ID
        - cd ...

frontend:
  phases:
    build:
      commands:
        - pnpm turbo build
  artifacts:
    baseDirectory: apps/placeholderapp/dist
    files:
      - "**/*"
  cache:
    paths:
      - node_modules/**/*

Reproduction steps
fork my repo,
attempt to deploy on aws.

Hey @crafael23, thank you for reaching out. From the build logs the message
credentials could not be used to assume 'arn:aws:iam::<account-id>:role/cdk-hnb659fds-deploy-role-<account-id>-us-east-2', but are for the right account. Proceeding anyway.

indicating the role may have been deleted or this may also occur if the account has Service Control Policies that could be enforced on the IAM user/role on an account level within the organization.
Does local sandbox throw a similar error message?
On the IAM console, could you confirm if the role does exist? additionally, confirm if the account does not have any service control policies?

@ykethan , for the moment local sandbox doesn't produce the same error

I do have other proyects hosted, a nextjs app and a little react SPA. Its only this one that gives the the problem, if I remove backend  deployment completely from te amplify.yml the problem goes away.

@ykethan btw, because this is a test that I'm doing, I'm doing this on my personal root account. I've not touched Service control Policies.

Hey @crafael23, thank you for reaching out. From the build logs the message
credentials could not be used to assume 'arn:aws:iam::<account-id>:role/cdk-hnb659fds-deploy-role-<account-id>-us-east-2', but are for the right account. Proceeding anyway.�

indicating the role may have been deleted or this may also occur if the account has Service Control Policies that could be enforced on the IAM user/role on an account level within the organization.
Does local sandbox throw a similar error message? On the IAM console, could you confirm if the role does exist? additionally, confirm if the account does not have any service control policies?

I just verified and the role does exist.

Hey @crafael23, thank you for the information. For a quick confirmation, does the app have a service role attached in the general settings?

@ykethan , the field for the service role is empty. Comparing it to the other react spa that i have there is no differnece, but comparing it to another nextjs app that i have deployed it appears to only have AmplifySSRLoggingRole and its not editable.

I guess thats not what im supposed to do

@ykethan CDK deploy role doesnt have the amplify AmplifyBackendDeployFullAccess
Ill try it out in a second.

@ykethan
I'm unsure weather this are the right settings for this

Since I see that in the  yaml you provided has the approot on ./apps.

@crafael23 i was able to deploy this successfully using the following. could you try this and let us know if it deploys

version: 1
applications:
  - appRoot: .
    backend:
      phases:
        preBuild:
          commands:
            - npm install -g pnpm
            - corepack enable
            - pnpm install
        build:
          commands:
            - echo $AWS_BRANCH
            - echo $AWS_APP_ID
            - cd packages/amplify
            - pnpm exec ampx pipeline-deploy --branch $AWS_BRANCH --app-id $AWS_APP_ID
            - cd ../..
    frontend:
      phases:
        build:
          commands:
            - pnpm turbo run build --filter="./apps/placeholderapp"
      artifacts:
        baseDirectory: apps/placeholderapp/dist
        files:
          - "**/*"
      cache:
        paths:
          - node_modules/**/*
          - .pnpm-store/**/*

@crafael23 👋 , thanks for sharing the detailed information and glad to hear that you are now unblocked. We are marking this as a bug to optionally allow creating an IAM service role by default for all apps.


Syntax highlighting does not recognize Wiki-styled links.

Please select the area your Bug applys to. (Multiple selections are Possible)

[x] UI
[ ] Workbench
[ ] Publishing
[ ] Pods
[x] Markdown
[ ] Hierarchy
[ ] Graph
[ ] Misc (Choose this if your not sure)

Describe the bug
The textmate grammar file does not recognize the [[<wiki-link]] format and thus does not properly support syntax highlighting/coloring for it.
To Reproduce
Create a note with a wiki-styled link, enable Developer: Inspect Editor tokens and scope, then over over the relevant syntax to see that the wiki-links aren't properly detected.

Incorrect parsing.
Expected behavior
I exped the wiki-styled links to be recognized as a separate scope, with the enclosing brackets marked as a beginning & ending scope for those links.

Correct parsing of the links.
Desktop (please complete the following information)

OS: Windows 10 x64
Version - Dendron 0.34.0

Markdown Notes, with GPL v3, provides a syntax implementation which could be used as the basis for this: https://github.com/kortina/vscode-markdown-notes/blob/master/syntaxes/notes.tmLanguage.json

Thanks for the issue. Will be doing another sweep of our grammar files

this should be fixed in v52 of Dendron. please post here if not, otherwise this issue will auto close in 3 days


Investigate xmltestfailures

Hi @bladehr8, I'm your friendly neighborhood Microsoft Open Technologies, Inc. Pull Request Bot (You can call me MSOTBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.msopentech.com.

TTYL, MSOTBOT;

BTW all the ASPNET/ASPNETCORE stuff was renamed to DNX so you'll want to update that in the PR.

this has been fixed now.


New Application button missing in console after organization switch

Describe the issue:
The "New Application" button is missing after switching to a sub-organization and returning to the super organization.
How to reproduce:
Switch to a sub-org and return to the super org.
Environment information

Product Version: IS 7.0 Alpha

The issue is not reproducing in the latest pack. Hence closing this issue.
https://github.com/wso2/product-is/assets/24982871/603bc0c7-26a5-4073-8f62-28ce92c374fb


Test case Dependency overwrites priority in TestNG

Meta -
OS: Windows 7
Selenium Version: 2.53.0 WebDriver
Browser: Chrome
Expected Behavior - While Running Tests with the combination of dependency and priority through testNG the priority must have higher execution precision.
Actual Behavior - The Dependency overwrites the precision of priority.
Steps to reproduce - Please execute below mentioned simple Driver class.
package test.pack;

import org.testng.annotations.Test;

public class dependencyTest {

@Test(priority = 1)
public void testMethod001() {
    System.out.println("TC-1");
}

@Test(dependsOnMethods = { "testMethod001" }, priority = 1)
public void testMethod002() {
    System.out.println("TC-2");
}

@Test(dependsOnMethods = { "testMethod002" }, priority = 1)
public void testMethod003() {
    System.out.println("TC-3");
}

@Test(dependsOnMethods = { "testMethod001" }, priority = 2)
public void testMethod004() {
    System.out.println("TC-4");
}
}

######Output #######
TC-1
TC-2
TC-4
TC-3
PASSED: testMethod001
PASSED: testMethod002
PASSED: testMethod004
PASSED: testMethod003

Default test
Tests run: 4, Failures: 0, Skips: 0
Default suite

Total tests run: 4, Failures: 0, Skips: 0

Thanks for the report.
Closed as duplicate of #474


Error during compiling

Ruby version: 3.0.2
Rubyfmt git sha: I downloaded the tag version 0.7.6 and clone the trunk branch and was almost the same error.
Os: Debian 11
Cargo and Rust: 📦 v0.6.8-pre via 🦀 v1.61.0

Error during compiling
Output for the clone of trunk version:
...
   Compiling rubyfmt v0.6.8-pre (/home/andres/Documentos/Proyectos/rubyfmt/librubyfmt)
   Compiling unicode-normalization v0.1.19
   Compiling addr2line v0.12.2
error: failed to run custom build command for `rubyfmt v0.6.8-pre (/home/andres/Documentos/Proyectos/rubyfmt/librubyfmt)`

Caused by:
  process didn't exit successfully: `/home/andres/Documentos/Proyectos/rubyfmt/target/release/build/rubyfmt-84c65605c74b8343/build-script-build` (exit status: 1)
  --- stderr
  Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }
warning: build failed, waiting for other jobs to finish...
make: *** [Makefile:22: release] Error 101

Output for the tag 0.7.6 version:
...
   Compiling rubyfmt v0.6.8-pre (/home/andres/Documentos/Proyectos/rubyfmt-0.7.6/librubyfmt)
   Compiling unicode-normalization v0.1.19
   Compiling addr2line v0.12.2
error: failed to run custom build command for `rubyfmt v0.6.8-pre (/home/andres/Documentos/Proyectos/rubyfmt-0.7.6/librubyfmt)`

Caused by:
  process didn't exit successfully: `/home/andres/Documentos/Proyectos/rubyfmt-0.7.6/target/release/build/rubyfmt-84c65605c74b8343/build-script-build` (exit status: 1)
  --- stderr
  fatal: no es un repositorio git (ni ninguno de los directorios superiores): .git
  Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }
warning: build failed, waiting for other jobs to finish...
make: *** [Makefile:22: release] Error 101

What is not found? What I am skipping?

Hi everyone
the error is also reproduced on
...
[admin@cold-wood-vs rubyfmt]$ make all
bash -c "find target/release | grep -i 'librubyfmt-.*\.a' | xargs rm; exit 0"
rm: missing operand
Try 'rm --help' for more information.
cargo build --release
   Compiling rubyfmt v0.6.8-pre (/home/admin/rubyfmt/librubyfmt)
   Compiling ureq v2.1.1
error: failed to run custom build command for `rubyfmt v0.6.8-pre (/home/admin/rubyfmt/librubyfmt)`

Caused by:
  process didn't exit successfully: `/home/admin/rubyfmt/target/release/build/rubyfmt-0cebd5e6ffabadaa/build-script-build` (exit status: 1)
  --- stderr
  Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }
warning: build failed, waiting for other jobs to finish...
make: *** [Makefile:22: release] Error 101
[admin@cold-wood-vs rubyfmt]$

Ruby version: ruby 2.7.3p183 (2021-04-05 revision 6847ee089d) [x86_64-linux]
Os: Fedora release 32 (Thirty Two)
Cargo and Rust: package v0.6.8-pre via crab v1.62.0

I think this PRhttps://github.com/penelopezone/rubyfmt/pull/343 should help fix things, it did on my end at least.

I'm having the same error running on v.0.7.6:
...
   Compiling quote v1.0.7
   Compiling time v0.1.43
   Compiling dirs-sys v0.3.6
   Compiling filetime v0.2.14
error: failed to run custom build command for `rubyfmt v0.6.8-pre (/home/andre/rubyfmt/librubyfmt)`

Caused by:
  process didn't exit successfully: `/home/andre/rubyfmt/target/release/build/rubyfmt-10e29e57e70ed59b/build-script-build` (exit status: 1)
  --- stderr
  Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }
warning: build failed, waiting for other jobs to finish...
make: *** [Makefile:22: release] Error 101

I'm running it on an Ubuntu 22.04.1 LTS over a Linux 5.15.0-52-generic x86_64

@kupkovski  0.7.6 is an old version, this should be fixed on 0.8.0. Does updating the version work for you?


GHC 8 Support

A new stackage nightly is ready for GHC 8 (nightly-2016-05-26). http-streams was temporarily pulled from stackage for GHC 8 compatibility.
Links for reference:

https://github.com/fpco/stackage/blob/master/build-constraints.yaml#L1681
https://www.fpcomplete.com/blog/2016/05/moving-stackage-nightly-ghc-8

Here are the initial error messages from stack while trying to patch the issue:
Resolver 'nightly-2016-05-26' does not have all the packages to match your requirements.
    MonadCatchIO-transformers not found
        - http-streams requires -any
    snap-core not found
        - http-streams requires >=0.9 && <1.0
    snap-server not found
        - http-streams requires >=0.9 && <1.0
    User package flags used:
        - http-streams: network-uri = True

I believe some of the necessary changes have been made in snap-core:

https://github.com/snapframework/snap-core/pull/255

Cool. When snap lands in nightly that'll be good.
Do you happen to know where MonadCatchIO has gone? Is it in base now?

MonadCatchIO-transformers not in nightly because its marked unmaintained. We need it for the test suite; it appears to be the catch that was used in MonadSnap, and snap-core presently depends on it.

I'm not going to leave this much longer. I hope Snap will get onto GHC 8, but if it's not going to make it then perhaps I should use something else for the test suite. Anyone have any suggestions for a light HTTP server to embded in-process for http-stream's test suite?

I'm working on the Snap 1.0 release this weekend and am planning to have it out by August 7.

@mightybyte Hey Dough, awesome! Do you have a sense of how to deal with the MonadCatch thing? https://github.com/snapframework/snap-core/issues/256#issuecomment-229992026 makes a good point; seems like it's all that's needed.

Snap 1.0 solves the problem by using monad-control instead of MonadCatchIO-transformers.

Oh dear. After all that, I just discovered snap-server depends on http-streams for its testsuite target. That's inconvenient, seeing as how this project depends on Snap for its test suite. Anyway, stack test fails to resolve right now. Not sure what to do about that.

While constructing the BuildPlan the following exceptions were encountered:

--  Failure when adding dependencies:
      http-streams: needed (>=0.7 && <0.9), couldn't resolve its dependencies
    needed for package snap-server-<IP_ADDRESS>

Yeah, bootstrapping the test suites is a bit of a pain.  But the two test suites don't depend on each other.  They just depend on the libraries themselves.  So you should be able to build snap-server 1.0, then http-streams (whatever version supports snap 1.0), then the snap-server test suite, then the http-streams test suite.  I believe @gregorycollins has this set up on Jenkins (it's been sending messages to #snapframework).  Once we upload snap-server-1.0 to hackage it should be easier.

@mightybyte Hm. Right now I've got
resolver: nightly-2016-07-19
packages:
 - /home/andrew/vcs/haskell/io-streams-haproxy
 - /home/andrew/vcs/haskell/snap-core
 - /home/andrew/vcs/haskell/snap-server
 - .
flags:
  http-streams:
    network-uri: true

in stack.yaml because I'm having to get Snap from git master. I'm not sure what I can do to convince stack to go and build snap-server ignoring the dependency. You're right, of course; this will be easier when snap-server-1.0 is released.
(doing stack install snap-server to try and force it ahead of time doesn't do it)

I can't find any way to convince stack to build the library. I think I'm back to needing to remove snap-server as a dependency. We'll have to find some other way to test our code.
[I'm pleased that you chose to use http-streams in your test suite, of course]

Can you just manually run the tests using cabal-install once before you release?  This problem should go away once we release snap which is still on track for happening in a week and a half.

@afcowie You can use the following stack.yaml file, plus the obviously needed changes to your .cabal file:
resolver: nightly-2016-07-27

packages:
- .
- location:
    git: https://github.com/snapframework/snap-server
    commit:<PHONE_NUMBER>f406944d325b1575d7e2b588da7c92
  extra-dep: true
- location:
    git: https://github.com/snapframework/snap-core
    commit: 3f49a1662cad466861b5ec4b1e88812328d26b1b
  extra-dep: true
- location:
    git: https://github.com/snapframework/io-streams-haproxy
    commit: ee84473f6fe3a6049a40ea4156277efcfde37603
  extra-dep: true

flags:
  http-streams:
    network-uri: true

I've confirmed that it finds a build plan, but it's still in the process of building.

Merged. Tests pass on GHC 7.10 and 8.0 now. Most excellent. Thanks @snoyberg Do you want me to [re]submit http-streams to nightly? I can't remember whether it's library build or test build that has to pass to be in (if just library, then I don't need to wait on Snap 1.0 getting in)

Please do. There's a section for skipped tests in the yaml configuration
file, please just add http-streams there too so it doesn't complain about
the lack of a compatible snap.
On Fri, Jul 29, 2016, 1:48 AM Andrew Cowie<EMAIL_ADDRESS>wrote:

Closed #96 https://github.com/afcowie/http-streams/issues/96.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/afcowie/http-streams/issues/96#event-738552386, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AADBB7gx27ij_V3HkTWZZPWa7blKzompks5qaTHSgaJpZM4In_lp
.


Live

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/windows-iotcore-docs, working directory: W:\yr3s-s, target branch: master, target branch commit: da06fe5090edff5be7c6631a6006fffa6966b82f, source branch: live, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/TOC.md
:white_check_mark:Succeeded

windows-iotcore/develop-your-app/IoTCoreShell.md
:white_check_mark:Succeeded

windows-iotcore/learn-about-hardware/SuggestedBoards.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Tell resizer to buffer inputs and outputs

When investigating a timing issue, I noticed a huge amount of delay on
an input. Using AES as an example:
Fanout     Cap    Slew   Delay    Time   Description
-----------------------------------------------------------------------------
                  0.00    0.00    0.00   clock clk (rise edge)
                          0.00    0.00   clock network delay (ideal)
                          5.18    5.18 ^ input external delay
                 19.80   14.14   19.32 ^ reset_n (in)
  2739    8.94                           reset_n (net)
                 19.80    0.00   19.32 ^ _35376_/RESET_B (sky130_fd_sc_hd__dfrtp_4)
                                 19.32   data arrival time

Enabling input buffering fixes this, and the design makes timing.

Should we add a config option for this? If so, do we want separate input and output options?

@antonblanchard: I applied this PR as a patch into my fork https://github.com/agorararmard/openlane/tree/buffer-ports, I added the configuration controls and separated inputs from outputs. I'll start a regression run over the design test set to see the effects of enabling the different combinations and disabling them. Then, I'll re-open another PR. If the results make sense.
So, for now, I'm closing this PR. Thanks!

Thanks @agorararmard!


Add initial implementation.

Including project setup, travis.yml and documents.

Review by @sjrd.

That's all, I think.

What is keepAlive? What does it do? Why is it useful?

That's all.

When keepAlive is true the instances of the browsers are not closed after the execution finishes. It was one of the features that was listed in https://github.com/scala-js/scala-js/issues/2168.
It is mostly meant as a way to debug directly in the browser console after a failure. It seems to be useful with run but I would avoid using it in test. Personally I found it quite useful while developing this PR.

When keepAlive is true the instances of the browsers are not closed after the execution finishes. It was one of the features that was listed in scala-js/scala-js#2168.

OK

LGTM


node2 debug adapter sometimes not returning response for launch request

I have written an integration test that tests debug starting.
However this integration tests fails on a build machine every 10th time on average. It always works locally.
After writing a lot of console.log as the only way to debug it when it runs on a build machine I have come to believe that the node2 debug adapter sometimes does not return a response for the launch request.
Even though the respone is not returned, node2 continues normally and sends all the initialized, variables and all other responses.
As a workaround for the intregration tests to always pass I am no longer awaiting on the start debugging, but just await on the initialized and everything else. And this seems like a fine workaround for now. However I wanted to create this issue to see if you have some ideas what might be wrong and why would node2 randomly not return from the launch request even though it launches just fine.
Example of a failed integration tests with my "logging"
https://dev.azure.com/vscode/VSCode/_build/results?buildId=36396&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=db522a89-84be-55c1-d087-ef4dde315b47
For reference here's the debug intregration test in question
https://github.com/microsoft/vscode/blob/5835d42bdf2f683c703de611f9043171953a1f35/extensions/vscode-api-tests/src/singlefolder-tests/debug.test.ts#L75
fyi @weinand and @connor4312 for potential ideas.

@isidorn are you sure that there is really no response?

there should be a timeout in VS Code in this case.
some debug adapters trigger their initialization sequence from within processing the launch request. That delays the launch response until after the configurationDone request. See second diagram in https://github.com/microsoft/vscode/issues/4902#issuecomment-368583522

@weinand I am not 100% sure, but it looks like that. Due to it not being easy to debug I stopped my investigation and outlined all the information I found above.
If there was a timeout there would be an error response and the tests would fail, not just await infinitly.
Even if the launch response would come after the configuartionDone the test would pass. It is written in a way to not care in what order they come, they just both have to arrive. Also that would not explain the flakiness.

Would it be possible to start the DA with the 'trace' parameter, then write out the log from the DA?

@roblourens yes I can do that. However the problem with that it is not so easy to reach the output files on the build machine.
For that I need to do specify the file as an asset which can later be downloaded. And as far as I see the debug adapter picks a file randomly?
Is there a way that I tell the debug adapter where it should write the logs and that it simply writes them there?

You can set "trace": "verbose" then the DA will send all logs as Output events and you can make sure those get console.logged. Or you can find the output event with the path of the file and have your test code read it and write that to the console.

I have changed the intregration tests to run with the new node debug. And so far they seem to work fine.
However to help you identify the node2 issue, I have re-ran the old tests with the trace verbose, and here's a test that fails.
https://dev.azure.com/vscode/VSCode/_build/results?buildId=37031&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d2c76452-9b5b-53aa-b9e7-4eac61843d9f
It has all the debug output in there. Sorry for the bad formatting!

All I can tell is that the adapter got the "launch" request and seems to have sent a response, and nothing crazy happened
0-02-11T10:39:31.4171438Z [7235:0211/103931.416291:INFO:CONSOLE(84)] "From client: launch({"type":"node2","request":"launch","name":"Launch debug.js","stopOnEntry":true,"program":"/home/vsts/work/1/s/extensions/vscode-api-tests/testWorkspace/debug.js","trace":"verbose","cwd":"/home/vsts/work/1/s/extensions/vscode-api-tests/testWorkspace","__nodeVersion":"v12.13.0","logFilePath":"/tmp/tmp.G3mJU0ZLqN/logs/20200211T103926/exthost1/ms-vscode.node-debug/debugadapter.txt","__debuggablePatterns":["*.js","*.es6","*.jsx","*.mjs"],"__sessionId":"1c1f3976-9c5c-49e6-838a-ba062e21b2ee"})
2020-02-11T10:39:31.4171997Z ",
2020-02-11T10:39:31.4172722Z [7235:0211/103931.416393:INFO:CONSOLE(84)] "To client: {"seq":0,"type":"event","event":"output","body":{"category":"telemetry","output":"debugStarted","data":{"Versions.DebugAdapterCore":"6.8.7","Versions.DebugAdapter":"1.42.1","request":"launch","args":["type","request","name","stopOnEntry","program","trace","cwd","__nodeVersion","logFilePath","__debuggablePatterns","__sessionId","enableSourceMapCaching","sourceMapPathOverrides","smartStep","sourceMaps","showAsyncStacks"]}}}

Thanks for looking into it. Yes the flakiness also happens with the new javascript debugger (only discoverd this over the night) just rarer than with node2.
So my main suspect is the communication implementation on the vscode side. Particularly the queueing of messages here
I will try to get more details today.

The queue communcitaion does not seem to be the case. My latest suspicion is that the test actually takes more than a minute to finish sometimes. Increasing timeout and checking if it helps

Leaving for next debt week unfortunetly.

I have reanabled the test and now they have one more retry. So if they fail two times in a row, only then they fail. That is the best approach I could find since the flakiness on the build machine was very hard to investigate further.
Alternative idea from @bpasero is to use Mock debugger instead of node to not have to launch a process which might reduce flakiness. Missing piece there is that mock debug is not a builtin extension so we would have to somehow install it. We could have a command line argument, but we can look into that if this retry attempt fails.


Plots sections: enable linking in the plots tooltips, other improvements

Plots section descriptions.

[ ] put links to DVC docs in those tooltips, probably means they should toggle by a click / ESC, not disappear
[ ] keep all three sections visible (for better education(, if section is empty, show the same message instead of it's content

Originally posted by @shcheklein in https://github.com/iterative/vscode-dvc/pull/1922#discussion_r901176891

I feel like this repo needs a ux issue label.

We had it before. I just want to understand what is the reason for changing as it makes sense if the description is dynamic. Please clarify it for me. Thanks

I think @shcheklein meant that instead of tooltips we should have the text visible under each Plot type header

No, we don't want this text to be permanently visible. Only as (potential) way for placeholders when there are not plots in the section.
tooltip should stay as a tooltip but react properly considering that there will be links

I've updated the description, there was a bug -  should not toggle ->  should toggle

I think I have a good solution for this. I will share the concept soon

@jorgeorpinel , here is a solution I believe in :) Sharing the example below. Tomorrow I will design the example of a hint including a button (or another link example).
Concept: show hint on hover with the mouse over the transparent area so the user can move the cursor into the hint area without it disappearing. When the mouse is out of the hint area - we hide it.
This will work also for other similar sections, such as coming errors: DVC errors that may occur during or after running experiment #1636
Example from our favourite GitHub
https://user-images.githubusercontent.com/98249521/175198240-0b9379ca-967d-46e6-83d0-b645e4959874.mov

Minor: the hints are not context menus, this is why I suggest we will have them centred in relation to the hovered element. Thanks

The Figma spec was updated with the new concept. Please let me know if you have any questions or comments.

This is a transparent area that appears when the icon has hovered. Find more information in the Figma spec
We could use a button here, but I think that text link works better for this case.

Relates to #1954.

Hey. What is the status of this ticket? Are we all agreed it is ready for development? Thanks

What are the links we want to put it? Once #2140 is merged, everything is ready to put in links, but I can also add them inside that PR.

@sroy3 let's wait for https://github.com/iterative/dvc.org/pull/3830 to be merged, @dberenbaum has changed the structure there. We can put those link later, we can create and assign to me a small followup ticket so that we don't block this PR.


Deleting build/compose_reports results in a missing error that does not get fixed when rerunning the task

Performing following steps:

Run <variant>ComposeCompilerCheck gradle task
Delete build/compose_reports
Run <variant>ComposeCompilerCheck gradle task again

Will result in an Directory '.../build/compose_reports' not exists error.
It seems Kotlin plugin does not include this directory as part of the UP-TO-DATE checks. I have made a ticket for them: https://youtrack.jetbrains.com/issue/KT-70509
At first glance, a workaround would be to simply add this folder to the output of the Kotlin tasks:
tasks.withType<KotlinCompile>() {
    outputs.dir(project.layout.buildDirectory.dir("compose_reports"))
}

However, this will cause all Kotlin tasks in a module to invalidate each other. That means that, for example, when main kotlin kotlin task generates compose_reports, it would invalidate ksp kotlin task and so on.
Ideally, all different kotlin tasks in a module should have a different output directory and then maybe a merger task that merges them into a single report?

@matejdro this is tangentially related to the other issue you opened up. i was (incorrectly) assigning the output directory of the check task as an input of the check task so it'd re-run correctly in this scenario.
what are your thoughts on this:
        project.tasks.withType(KotlinCompile::class.java).configureEach(
            object : Action<KotlinCompile<*>> {
                override fun execute(t: KotlinCompile<*>) {
                    t.outputs.upToDateWhen {
                        // where checkExtension.outputDirectory is the build/compose_reports folder by default
                        checkExtension.outputDirectory.get().exists()
                    }
                }
            }
        )

I added ksp to my sandbox app and as a test followed this and it seems like everything was working as expected:

run ./gradlew :feature:debugComposeCompilerCheck
run ./gradlew :feature:kspDebugKotlin
delete build/compose_reports
re-run ./gradlew :feature:debugComposeCompilerCheck
See build/compose_reports correctly generate as compile task executed
re-run ./gradlew :feature:kspDebugKotlin
see no tasks execute, configuration cache used

This can still be vulnerable to this:

Run ./gradlew :feature:debugComposeCompilerCheck
Run ./gradlew :feature:releaseComposeCompilerCheck
Delete build/compose_reports
Run ./gradlew :feature:debugComposeCompilerCheck
Run ./gradlew :feature:releaseComposeCompilerCheck

Step 5 will fail because folder will exist, but relevant files in that folder will not.

Also found a similar problem with the build cache, if you want, I can create a separate ticket for this:

Run ./gradlew clean
Run ./gradlew :feature:debugComposeCompilerCheck --build-cache
Run ./gradlew clean
Run ./gradlew :feature:debugComposeCompilerCheck --build-cache

Check will fail with compose_reports not exists error

2. ./gradlew :feature:releaseComposeCompilerCheck

can rectify that with a bit smarter of a upToDateWhen check
                    t.outputs.upToDateWhen {
                        checkExtension.outputDirectory.get().listFiles()?.any {
                            it.name.contains(variant.plus("-composables.txt"))
                        } ?: false
                    }

Also found a similar problem with the build cache, if you want, I can create a separate ticket for this:

Run ./gradlew clean
Run ./gradlew :feature:debugComposeCompilerCheck --build-cache
Run ./gradlew clean
Run ./gradlew :feature:debugComposeCompilerCheck --build-cache

Check will fail with compose_reports not exists error

created a new issue for this!

@matejdro I uploaded a 2.2.2-alpha that I think addresses all open issues. would you be willing to give it a spin and let me know if you run into anything? It's appreciated!

Thanks for looking into it!
It seems I can still do this:

Add some unstable composables, so the compiler check should fail
Run ./gradlew :feature:debugComposeCompilerCheck <- this should fail with reporting unstable composables
Delete all files in the build/compose_reports
Run ./gradlew :feature:debugComposeCompilerCheck <- this time, task passes even though there are unstable composables inside

I did some experiments with setting the same upToDateWhen for the kotlin compile task and it seems to fix above issue.

verified the above is addressed in upcoming 2.2.4-alpha

I can still reproduce above steps. The issue is that, even after deleting compose_reports, debugComposeCompilerCheck is still UP-TO-DATE.
I think this task should never be up to date when there are reported unstable composables? Even if you run it twice without changes, it should fail both times.

I am unable to repro unfortunately using the latest published version. I have recorded a video, am I performing a different set of steps than you?
https://github.com/user-attachments/assets/d877366c-919c-420b-85f6-70a091322bab

Yes, your steps are different. My step mentions to delete all files from the folder instead of deleting whole folder.

Also, similarly:

Add some unstable composables, so the compiler check should fail
Run ./gradlew :feature:debugComposeCompilerGenerate
Run ./gradlew :feature:debugComposeCompilerGenerate <- this should not fail, because unstable composable is now in the baseline
Manually edit my-module/compose_reports/...-composables.txt and remove unstable composable from it
Run ./gradlew :feature:debugComposeCompilerCheck <- this time, task passes even though unstable composable is no longer in the baseline

Yes, your steps are different. My step mentions to delete all files from the folder instead of deleting whole folder.

ah okay, I see it now and can repro. Will fix in 2.2.7-alpha

Also, similarly:

Add some unstable composables, so the compiler check should fail
Run ./gradlew :feature:debugComposeCompilerGenerate
Run ./gradlew :feature:debugComposeCompilerCheck <- this should not fail, because unstable composable is now in the baseline
Manually edit my-module/compose_reports/...-composables.txt and remove unstable composable from it
Run ./gradlew :feature:debugComposeCompilerCheck <- this time, task passes even though unstable composable is no longer in the baseline

fixed in 2.2.7-alpha

Seems to be indeed fixed. Thanks!


Add document with process for updating source-build for 2.1

Fixes #346

/cc @jaredpar @omajid for awareness and input.


Latest Version of SoftEther VPN Server on x86_64 Ubuntu Breaks L2TP/IPSec Connections

Hello!
The latest version of SoftEther VPN Server on x86_64 Ubuntu breaks connections initiated from Windows XP, which renders the system to be stuck at "Connecting to <IP_ADDRESS>" instead of entering next phase of "Verifying user name and password...". This issue does not occur on Windows Vista and onwards. Can someone fix the issue?

[ V ] Can you reproduce? -> Yes!
[ V ] Are you running the latest version of SoftEtherVPN? -> Yes

**SoftEther version: Ver 4.27, Build 9668, beta
Component: Server
Operating system: Ubuntu 18.04 LTS
Architecture: 64-bit
Processor:: Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz
Description
Clients from Windows XP cannot establish connections to VPN server via L2TP/IPSec protocol.
Expected behavior:
Connections should be established successfully instead of hanging there.
Actual behavior:
Connections from Windows XP hang at "Connecting to W.X.Y.Z" instead of entering "Verifying user name and password..." phase.
Steps to reproduce

Setup SoftEther VPN Server on x86_64 Ubuntu.
Establish L2TP/IPSec connections from Windows XP.
Windows XP cannot make connections to the server.
Try with Windows Vista and onwards to establish VPN tunnels via L2TP/IPSec.
Vista and onwards can reach the server and establish VPN tunnels via L2TP?IPSec successfully.

Hope to get your reply soon.
Thanks! Much appreciated!
Regards,
Andy

windows XP is out of support from Microsoft.
Not even Firefox supports it.
you should move away from/upgrade it.
Use openvpn 2.3.18 as alternative

Ver 4.27, Build 9668, beta is related to https://github.com/SoftEtherVPN/SoftEtherVPN_Stable
anyway, I could not find a way to download WinXP, it's support ended.
can you try the following - install several latest builds and check every build on WinXP compatibility ?
thus we can find the change that breaks WinXP

I confirm this issue. The latest server build that runs properly on WinXP SP3 (no other Windows versions tested, just XP) is "softether-vpnserver_vpnbridge-v4.25-9656-rtm-2018.01.15-windows-x86_x64-intel.exe". I tested ALL higher versions (they are all betas) one by one and they all failed.

I confirm a similar issue.I am running SoftEther VPN server under winXP SP3 machines. The latest server build that runs properly on WinXP SP3 (no other Windows versions tested, just XP) and can successfully accept incoming L2TP connections is "softether-vpnserver_vpnbridge-v4.25-9656-rtm-2018.01.15-windows-x86_x64-intel.exe". I tested ALL higher versions (they are all betas) one by one and they all failed.

4.X is "stable" repo.
since 4.25-9656 there were 5 commits:
https://github.com/SoftEtherVPN/SoftEtherVPN_Stable/compare/v4.25-9656-rtm...master
we can try them one by one and have a look which one breaks WinXP
unfortunately, I do not have an WinXP here (and I have no idea where to get it).
can you try to find the breaking change ?

@501ari5 , I've managed to get WinXP image. couple of questions

are you using x86 or x64 build of WinXP ?
are you using SP3 on WinXP ?
which ubuntu do you use ? 18.04 ?

Superseded by #688.


Implement Wallet Discovery For Multichain API #2970

Addressing Implement Wallet Discovery For Multichain API #2970
feat: support CAIP294 (standardized messaging transport for browser extension wallets)
feat: make sure we pass in extensionId when announcing wallet

@metamaskbot build-previews

@metamaskbot publish-preview


App is spazzing out

Also, There needs to be server folder support and clicking on a server should open the first channel in the list

Here's a link to download the Insider version: https://www.microsoft.com/store/apps/9NN1ZFD5G6DL
A full rewrite is coming out in a month. The current insider build does not have server folders, however the most recent commit on the rewrite branch does. This issue is for the old Quarrel so I'm going to close it


feat(npm): update to publish to npm package

Description of change

Pull-Request Checklist

[ ] Code is up-to-date with the main branch
[ ] npm run lint passes with this change
[ ] npm run test passes with this change
[ ] This pull request links relevant issues as Fixes #0000
[ ] There are new or updated unit tests validating the change
[ ] Documentation has been updated to reflect this change
[ ] The new commits follow conventions outlined in the conventional commit spec

:tada: This PR is included in version 1.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Match An Emoji in String

How to match emoji in text Field
Basically i want to check My Typed Message is only Emoji or with text

The package doesn't offer a direct helper method for that but you should be able to just check your text with regex for words or letters. Or seems there is also a package called emoji_regex, not sure if it is helpful tho.

A bit complex, but it should be possible to create this regex and then check every character in your string
    final regExBuffer = StringBuffer();
    for (final list in defaultEmojiSet) {
      for (final emoji in list.emoji) {
        // Put emoji inclusive skin tone before actualy emoji
        // to avoid color and emoji being seperated
        if (emoji.hasSkinTone) {
          for (final skinTone in SkinTone.values) {
            regExBuffer.write(
              '${utils.applySkinTone(emoji, skinTone).emoji}$delimiter',
            );
          }
        }
        regExBuffer.write('${emoji.emoji}$delimiter');
      }
    }
    final regExString = regExBuffer.toString();
    RegExp regex = RegExp(regExString.substring(0, regExString.length - 1));


How can I add babel-polyfill to config file

The IE and firefox need to add babel-polyfill to support ES6, for example  Promise and so on

This is supported out of the box in CRA, you just need to set IE and older Firefox versions in your browsers list, please refer to CRA docs for this.


Switch MongoDB libraries. Update test data.

Detail in https://github.com/influxdata/telegraf/pull/9493 .

Reset c.tlsCfg.ServerName between multiple certs/sources to fix issue.
https://github.com/influxdata/telegraf/pull/9289


fix references to requirements.txt

This PR:

fixes the ReadTheDocs references to requirements-dev.txt

Codecov Report

Merging #147 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #147   +/-   ##
=======================================
  Coverage   95.95%   95.95%
=======================================
  Files           8        8
  Lines         445      445
=======================================
  Hits          427      427
  Misses         18       18

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c726a26...cf5b4eb. Read the comment docs.


The picker telescope and lua-fzf got hang when the variable has multi underscore

I tried to run
Cscope find g __sk_buff

in the linux kernel source tree, some of the pickers were hanging.

quickfix - ok
telescope - hung
lua-fzf - hung

Cause is not multi underscore but treesitter.
file - tools/include/uapi/linux/bpf.h
If you try to open result in quickfix, nvim hangs.
nvim hangs when opening/previewing this file.
I'm not even able to open this file in nvim when treesitter is turned on.
➜ nvim tools/include/uapi/linux/bpf.h

I'll advise turning off treesitter for now and raise issue in nvim-treesitter

nvim-treesitter/nvim-treesitter#5227

Thank you!!

I can open the bpf.h in nvim without issues, but when telescope runs as a picker to show the file, nvim is hanging. So it sounds like a different issue between us?

 My config loads it on BufRead event.

I believe so, I didn't put customized config but just the default config below
use { 'nvim-treesitter/nvim-treesitter', run = ':TSUpdate' }

@waynecw
Lazy loading doesn't affect it (I tried with and without)
Can you try on latest nvim nighlty? It has some improvements for injection handler neovim/neovim#24647

I tried nvim nightly but still got hang.
Below is my step.

Checkout libbpf from https://github.com/libbpf/libbpf. My git hash is at 05f94ddbb837f5f4b3161e341eed21be307eaa04.
Run cscope -R -q -k
Check nvim version

nvim --version
NVIM v0.10.0-dev-800+g3d948a4dc
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3

In nvim, run PackerSync to make sure plugins are the latest
In nvim, run Cscope find g bpf_sock.
In telescope picker, select the file include/uapi/linux/bpf.h, then nvim hangs

You are not on latest nightly. g3d948a4dc doesn't contain injection handler patch.
gc0ac53e0d is the latest one as of this moment.

I switched to gc0ac53e0d and now it works perfectly, thanks a lot!


Add simplified custom workflow capability

Adds a super simple custom workflow. Based on @cansavvy 's work and the discussion here: https://github.com/jhudsl/AnVIL_Template/pull/64
OTTR should:

Ignore custom-workflow.yml
Ensure repos downstream can add customization without OTTR syncs overwriting anything.

See the custom-workflow file here https://github.com/jhudsl/AnVIL_Template/pull/64 for an idea of what a custom workflow might entail.

Is this working? Do we want to keep it? I lost track of what the implemented solution was over on https://github.com/jhudsl/AnVIL_Template ?

@cansavvy Let me make a few more tweaks to update things here.
Is staging up to date? Seems like a lot of changes in the diff!!

@cansavvy Let me make a few more tweaks to update things here.
Is staging up to date? Seems like a lot of changes in the diff!!

Staging was not up to date :sad: But it should be now.

@cansavvy all good here, as long as you are good with it! I guess we want to exclude the custom workflow file from the sync right?

The more I'm thinking about it, I feel like this is more a place for a "baby ottr" and not something we want to automatically have in the main OTTR_Template. What do you think, @avahoffman ?

I am okay with whatever! I do think we need to make sure that there's an easy way to avoid overwriting workflows that are created by spinoffs. Did you have something else in mind?


HTTP Request Error in Google App Engine

For certain requests, like GET detailed rates, GAE throws a ChunkedEncodingError. I believe this can be fixed using monkeypatch (described here in the 2nd solution).
So in config.py imports, you might be able to just add:
import requests
import requests_toolbelt.adapters.appengine
requests_toolbelt.adapters.appengine.monkeypatch()

Thanks for raising the issue and suggesting a solution Roy. We have discussed with the maintainers and after evaluating the pros and cons we have decided not to implement a fix for now.
We aim to target the widest possible set of use cases, and where possible we try to explicitly declare and isolate dependencies. Implementing the monkeypatch will break that principle for users not running on GAE.
You are however more than welcome to enhance the SDK for your particular needs.


[New game]: The simon Game

🎮 Game Request
The Simon Game is a classic memory game that tests your ability to remember and repeat a sequence of colors and sounds. This version of the game was built using HTML, CSS, and JavaScrip
Point down the features

Watch and listen carefully as the game plays a sequence of colors and sounds.
Repeat the sequence by clicking on the colored buttons in the correct order.
If you get the sequence right, the game will play another sequence, this time with one extra color and sound.
Keep repeating the sequences correctly to advance through the levels.
If you make a mistake, the game will end and you'll have to start over from the beginning

Select program in which you are contributing
No response
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Babunshil !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @Babunshil!
We are already having a similar game request in #348 👀
Make sure you come up with a cool unique idea 😀
Waiting for your new game idea 💗.


Settings suggestions are broken

Latest insiders or out of dev

settings.json
Trigger intelli-sense - no suggestions

This makes it impossible to discover settings.

Duplicate #21704


Text widget unexpectedly breaks Arabic text in multiple lines on Android (but not on iOS)

Steps to Reproduce
Some Arabic texts have unexpected breaks inside. This happens on Android, but not on iOS, while the apps are built from the very same codebase. Can reproduce it with the Flutter 3.0.1. Didn't try any other version yet.

Create a basic Flutter app with displaying just a single Text widget with some specific text like "شكراً"
Build and start both Android and iOS apps.
Observe the text on the screen.

Expected results: Both Android and iOS display the text in the same way - in just one line.
Actual results: iOS displays the text correctly, while Android renders the text in multiple lines.

Code sample

import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const Scaffold(
        body: Center(
          child: Text("شكراً"),
        ),
      ),
    );
  }
}

Logs
[✓] Flutter (Channel stable, 3.0.1, on macOS 12.4 21F79 darwin-x64, locale en-GB)
    • Flutter version 3.0.1 at /Users/user/Developer/Flutter/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision fb57da5f94 (5 days ago), 2022-05-19 15:50:29 -0700
    • Engine revision caaafc5604
    • Dart version 2.17.1
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0-rc1)
    • Android SDK at /Users/user/Library/Android/sdk
    • Platform android-32, build-tools 32.0.0-rc1
    • ANDROID_HOME = /Users/user/Library/Android/sdk
    • Java binary at: /Users/user/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/212.5712.43.2112.8512546/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Users/user/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/212.5712.43.2112.8512546/Android
      Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] Android Studio (version 2021.1)
    • Android Studio at /Users/user/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/211.7628.21.2111.8309675/Android
      Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)

[✓] Android Studio (version 2021.1)
    • Android Studio at /Users/user/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/211.7628.21.2111.8193401/Android
      Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)

[✓] IntelliJ IDEA Community Edition (version 2022.1.1)
    • IntelliJ at /Users/user/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5591.52/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] IntelliJ IDEA Community Edition (version 2022.1)
    • IntelliJ at /Users/user/Library/Application Support/JetBrains/Toolbox/apps/IDEA-C/ch-0/221.5080.210/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.66.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.38.1

[✓] Connected device (4 available)
    • sdk gphone x86 64 arm64 (mobile)    • emulator-5554                        • android-x64    • Android 11 (API 30) (emulator)
    • iPhone SE (3rd generation) (mobile) • 074DADAE-6C47-4DBF-945F-A1262EEEFBA3 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-5
      (simulator)
    • macOS (desktop)                     • macos                                • darwin-x64     • macOS 12.4 21F79 darwin-x64
    • Chrome (web)                        • chrome                               • web-javascript • Google Chrome 101.0.4951.64

[✓] HTTP Host Availability
    • All required HTTP hosts are available

I made additional tests and must say that:

Flutter 3.0.1 also has this issue
Flutter 2.10.5 doesn't have it

See https://github.com/flutter/flutter/issues/103846

Hi @Javernaut,
There is a similar issue describing this case https://github.com/flutter/flutter/issues/103846, Please follow up there for further updates, Closing this issue as a duplicate. If you disagree feel free to write in the comments and we will reopen it.
Thank you.


Fixup - various feedbot bugs

Changes

Fixes the issue where tasks are sent to the backend rather than the feedbot
Fixes nil pointer error that's caused when there is no previous collection token added event
Fixes errors in retrieving NFT events because of type mismatch

Testing

Tested changes locally and also deployed backend to sandbox

Looks awesome, Jarrel! One small request: since the "feedbot" and "tasks/feed-event" parameters are reused in several places, could we make a wrapper method like "createTaskForFeedbot" that calls createTaskForService with the correct parameters? Or is there a case where we'd expect the feedbot to potentially pass in different parameters?

Great idea! Added the wrapper since I don't really see the feedbot needing more routes.


Refs #32695 -- Changed method that creates Permissions

https://code.djangoproject.com/ticket/32695

Closing per ticket.


Update react-console to 1.10.5

Pull Request Test Coverage Report for Build 426

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.956%

Totals

Change from base Build 423:
0.0%

Covered Lines:
1332

Relevant Lines:
1477

💛  - Coveralls


update description of the categories

Related #1 #69
I added some descriptions, but this PR is mostly to define the short descriptions to be included into config.yml (lot of definitions still needed).
I added Languages.
I belive that the general categories (Cores, Frameworks, any without a :) don't need a short description.

Only 22 of 79 items has the categories field (and some can be wrong). We need to be clear the categories to produce a good categorization.

Only 22 of 79 items has the categories field (and some can be wrong). We need to be clear the categories to produce a good categorization.


Python, printing left and right hand landmarks for the holistic model in colab.

print(
f'Right Hand:\n'
f'{results.right_hand_landmarks.landmark}'
f'Left Hand:\n'
f'{results.left_hand_landmarks.landmark}'
)
when running the python holistic in colab. im printing out the hand landmark coordinates for the photo. when doing this it prints the landmarks x,y,z correctly for a SINGLE image. but it doesn't work when trying to use multiple images at once. it gives the error
AttributeError                            Traceback (most recent call last)
 in ()
31
32   print(
---> 33     f'Right Hand:\n'
34     f'{results.right_hand_landmarks.landmark}'
35     f'Left Hand:\n'
AttributeError: 'NoneType' object has no attribute 'landmark'
as soon as it gets to trying to print the right and left hand landmarks for the second image. does anyone know why it does this? and how to fix it? again, it works only for the first image until it gets to the second one

nevermind, i got it

nevermind, i got it

could you give me information to fix it? I face this problem too

I meet the same problem.Could you give me some information?

you can visit my solution here https://github.com/google/mediapipe/issues/1803


Not starting in Sketchup 2024

Extension Errors Report
SketchUp: 24.0.484
OS: Windows 10
Ruby: 3.2.2

Extension: Ruby Console+ (3.1.7)
Error: TypeError (allocator undefined for #<Class:0x0000018f595f9f80>)
C:/Users/hannes/AppData/Roaming/SketchUp/SketchUp 2024/SketchUp/Plugins/ae_console/core.rb:125:in `new'
C:/Users/hannes/AppData/Roaming/SketchUp/SketchUp 2024/SketchUp/Plugins/ae_console/core.rb:125:in `initialize_plugin'
C:/Users/hannes/AppData/Roaming/SketchUp/SketchUp 2024/SketchUp/Plugins/ae_console/core.rb:213:in `<module:ConsolePlugin>'
C:/Users/hannes/AppData/Roaming/SketchUp/SketchUp 2024/SketchUp/Plugins/ae_console/core.rb:3:in `<module:AE>'
C:/Users/hannes/AppData/Roaming/SketchUp/SketchUp 2024/SketchUp/Plugins/ae_console/core.rb:1:in `<top (required)>'
C:/Program Files/SketchUp/SketchUp 2024/Tools/extensions.rb:197:in `require'
C:/Program Files/SketchUp/SketchUp 2024/Tools/extensions.rb:197:in `load'
C:/Users/hannes/AppData/Roaming/SketchUp/SketchUp 2024/SketchUp/Plugins/ae_console.rb:26:in `register_extension'
C:/Users/hannes/AppData/Roaming/SketchUp/SketchUp 2024/SketchUp/Plugins/ae_console.rb:26:in `<module:ConsolePlugin>'
C:/Users/hannes/AppData/Roaming/SketchUp/SketchUp 2024/SketchUp/Plugins/ae_console.rb:7:in `<module:AE>'
C:/Users/hannes/AppData/Roaming/SketchUp/SketchUp 2024/SketchUp/Plugins/ae_console.rb:5:in `<top (required)>'

initializations fails @line 125, 139
Very dirty, quick solution, but stdout & stderr redirectors won't work (open Window>Developer>Ruby Console to see output).
is to remove new method at the above lines.

The latest version in source is 3.1.7 which works fine with SU2024. The latest under the Release page is out of date.
@Aerilius are you interested in assistance in mantaining this repo? We can assist in updating the Release section and even get it uploaded to Extension Warehouse.

I've updated the repository with my fixes and built a new release. It should work now in the current version of SketchUp.

and even get it uploaded to Extension Warehouse.

I have now a GitHub Action for building the .rbz, I don't know if it is possible to automate the submission as well.

Thank you!
I was using your console in a presentation at this year's Basecamp. Found that the attendees wasn't able to run it, which had me puzzled. I only just realized now that I was 3 patches ahead of them because I was running the extension from source (I had modified it for the presentation: https://github.com/thomthom/sketchup-console-plus/commits/dev/snippets/)
Atm there is no EW API, and the Trimble ID login system prevents bots (automation scripts) from signing in.
We would love for this to be on EW though, would make it much more accessible. (The presentation Chris F and I did was showing people that never touched code to not be afraid of code. And that Ruby and the SU API is a lot easier than they expect. Console+ fit well into that as we introduced the audience to tinkering.)