Code helper : High CPU usage on macOS Sierra

VSCode Version: 1.14.2
OS Version: macOS Sierra Version 10.12.5

Steps to Reproduce:

Open vs code
wait

Reproduces without extensions: Yes
ps aux | grep -i code
damien           29107 100,0  3,1  3428428 261784   ??  R     3:45     8:39.02 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/typingsInstaller.js --globalTypingsCacheLocation /Users/damien/Library/Caches/typescript/2.4 --enableTelemetry
damien           29165   0,0  0,4  3238904  29772   ??  S     3:46     0:01.34 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap --type=searchService
damien           29106   0,0  0,5  3318432  40732   ??  S     3:45     0:10.41 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript/out/utils/electronForkStart /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js --useSingleInferredProject --enableTelemetry --cancellationPipeName /var/folders/yn/660wq__n6js538lhbm47gd0c0000gn/T/vscode-tscancellation-378a3d8805953d4e2451.sock*
damien           28897   0,0  0,4  3158564  29432   ??  S     3:44     0:00.41 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/css/node_modules/vscode-languageclient/lib/utils/electronForkStart /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/css/server/out/cssServerMain.js --node-ipc
damien           28895   0,0  0,1  2464108  11160   ??  S     3:44     0:00.01 /Applications/Visual Studio Code.app/Contents/Frameworks/Electron Framework.framework/Resources/crashpad_handler --database=/var/folders/yn/660wq__n6js538lhbm47gd0c0000gn/T/VSCode Crashes --metrics-dir=/var/folders/yn/660wq__n6js538lhbm47gd0c0000gn/T/VSCode Crashes --url=https://rink.hockeyapp.net/api/2/apps/21a48a66799e47fea4f52c0ff81e803d/crashes/upload --handshake-fd=58
damien           28893   0,0  0,4  3232568  35024   ??  S     3:44     0:01.48 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap --type=watcherService
damien           28892   0,0  0,5  3247868  43104   ??  S     3:44     0:03.78 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap --type=extensionHost
damien           28881   0,0  0,8  3313816  64880   ??  S     3:44     0:01.28 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper --type=renderer --js-flags=--nolazy --no-sandbox --primordial-pipe-token=17E325E1422625ABDF38593DBB836E22 --lang=fr --node-integration=true --hidden-page --enable-pinch --num-raster-threads=2 --enable-gpu-rasterization --enable-zero-copy --enable-gpu-memory-buffer-compositor-resources --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,34037;0,11,34037;0,12,34037;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,34037;1,11,34037;1,12,34037;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,34037;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,34037;2,13,3553;2,14,34037;2,15,34037;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,34037;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,34037;3,13,3553;3,14,34037;3,15,34037 --service-request-channel-token=17E325E1422625ABDF38593DBB836E22 --renderer-client-id=6
damien           28880   0,0  1,7  4381240 143020   ??  S     3:44     0:36.70 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper --type=renderer --js-flags=--nolazy --no-sandbox --primordial-pipe-token=6B472CBBD9BAE0A2E8ED0AE61DAE4FC1 --lang=fr --node-integration=true --background-color=#1e1e1e --disable-blink-features=Auxclick --enable-pinch --num-raster-threads=2 --enable-gpu-rasterization --enable-zero-copy --enable-gpu-memory-buffer-compositor-resources --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,34037;0,11,34037;0,12,34037;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,34037;1,11,34037;1,12,34037;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,34037;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,34037;2,13,3553;2,14,34037;2,15,34037;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,34037;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,34037;3,13,3553;3,14,34037;3,15,34037 --service-request-channel-token=6B472CBBD9BAE0A2E8ED0AE61DAE4FC1 --renderer-client-id=4
damien           28877   0,0  0,8  2920532  63376   ??  S     3:44     0:10.28 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper --type=gpu-process --no-sandbox --supports-dual-gpus=false --gpu-driver-bug-workarounds=0,1,10,23,25,35,38,45,51,59,61,62,63,64,66,70,71,73,81,82,83,86,88,89 --gpu-vendor-id=0x8086 --gpu-device-id=0x5926 --gpu-driver-vendor --gpu-driver-version --gpu-driver-date --gpu-active-vendor-id=0x8086 --gpu-active-device-id=0x5926 --service-request-channel-token=3B0208FFC95A3A5EB09BA8F6066FB68D
damien           28876   0,0  1,1  3529428  94840   ??  S     3:44     0:11.94 /Applications/Visual Studio Code.app/Contents/MacOS/Electron
root             28548   0,0  0,1  2471644   5420   ??  Ss    3:39     0:00.03 /System/Library/Frameworks/Security.framework/Versions/A/XPCServices/com.apple.CodeSigningHelper.xpc/Contents/MacOS/com.apple.CodeSigningHelper
damien           27978   0,0  0,2  2557844  13716   ??  Ss    3:32     3:17.48 /System/Library/Frameworks/VideoToolbox.framework/Versions/A/XPCServices/VTDecoderXPCService.xpc/Contents/MacOS/VTDecoderXPCService
damien           30196   0,0  0,0  2451236   2004 s003  S+    3:56     0:00.00 grep -i code````

Extensions :

you can try restarting you mac, hope helpful

I am seeing this as well inside VS Code 1.14.2. To make matters worse, the Code Helper process is left running when I quit VS Code.

Here are some simple reproduction steps for this issue:

Open a terminal and change to your $HOME directory
Run code --disable-extensions .
Open Activity Monitor. Observe that the Code Helper process is running at well over 100% CPU usage. My guess is that this is caused by it parsing through the entire $HOME directory tree structure.
Quit code by pressing Cmd + Q. Inside Activity Monitor, observe that Code Helper is still running and its CPU usage is still over 100%. It does eventually go away.

The original authors process that is 100% seems to be TypeScript: damien           29107 100,0  3,1  3428428 261784   ??  R     3:45     8:39.02 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/typingsInstaller.js --globalTypingsCacheLocation /Users/damien/Library/Caches/typescript/2.4 --enableTelemetry

Following @jkwuc89's steps, I can confirm that it's freaking out, specifically in the $HOME directory:

I have the same problem. Vscode version is the newest 1.16.1 now. However the CPU level is so high and my mac got very hot. Although I quitted vscode, the two code helper processes are working background so that I must kill them by myself. I'm writing c++.

Ditto with VSCode 1.7X I just updated today. Even after quitting VSCode Code helper and it's python processes absorbed all the memory on my machine (disk and RAM). The only time I've ever seen Mac OS X complain about  system put of memory is the 2 times I've tried to use VSCode at work. Not sure what is going on but obviously there is some sort of run away processing going on with codehelper.
The code base I am using this on is a large C++ and C# code base.

I have the same problem with 1.17. What is strange is it only occurs to one project directory. Don't know why is that as other directory used to develop vue component seems all right. I have tried to set useExperimentalWater and add file.excludes etc. It is the same result.

@darkdescendant After I banned the Microsoft C++ extensions, my cpu level seems to be normal again. My Activity Monitor tells me the Microsoft C++ extensions make cpu in a high level. However, C++ extensions got updated yesterday and I didn't make a test. @xiaoshuw Vue I don't know...

Yeah, I figured it was that extension. But since that is the whole reason for me in using VSCode over Sublime it kind of kills it for me. :-(
I might re-install and see what happens since you noted the extension was updated.

Maybe this issue is related: https://github.com/Microsoft/vscode-cpptools/issues/1114

Well, mine doesn't have the C/C++ extension. Also, it doesn't have issues in one project but does have on another. As I am using the vscodevim, it renders the vscode useless because after one key stroke, it seems waiting for the run-away process so it effectively useless. I didn't have problem with 1.16, it only started after recent update.

High CPU on macOS is the number one thing that drives me nuts on VSCode and the very next thing is the fact that it's such a pain to debug. MS really needs to provide some tools outside of the standard Google Dev Tools (which don't make it easy).
What I want to see is that VSCode monitors resource usage and runaway extensions. I want to see a pop up or some other easy-to-read diagnostic along with an offer to disable the offending extension. The last thing I want to do is to spend so much time debugging my development tools themselves.

@sanghin Do you still see the originally reported TypeScript cpu issue on VSCode 1.18 insiders? If so, does this reproduce for all folders you open or just some of them?
For anyone seeing high cpu usage with the C++ extension, please try following up with that extension instead

I can no longer see the run away process anymore -- with the same 1.17. I didn't do anything - besides in between I have probably rebooted my machine a few times. I didn't use TypeScript. As I said earlier, I have two projects of similar setup. Only one project had this issue.

In fact, I think the C/C++ Extension gets much better after updating its version. These days there is only one time getting very hot but soon it gets normal cpu level.

@mjbvz Sorry for my late (late) response. This issue can be closed. I'm now on :

VSCode 1.17.2 (1.17.2)
High Sierra Version 10.13

I'm pretty sure that the issue was caused by an incomplete configuration of file.exclude and search.exclude options

It's still burning extremely hot in my $HOME folder on Mac:

Go to $HOME directory
type code --disable-extensions .
watch it burn:

I have the same issue with macos sierra, Code helper takes 100% CPU

Code Version 1.17.2 (1.17.2) is still burning extremely hot in my $HOME folder on Mac:

You should add some ignore rules in your user settings (files.exclude and search.exclude), vscode tries to index every files in your $HOME folder

I have added the rules but it didn't fix the issue. But finally I installed the old 1.17.2 version (instead of the 1.18) and it looks stable now

I had to uninstall Visual Studio because of high CPU usage with maximum of over 120% and minimum of 5% even at the lowest usage it is insane. Could not kill process, restart took more than few minutes.
I am using latest version and really wanted to like it due to it's very good look and feel and prebuilt extensions compared to other editors which has no control over external extensions.

@sanghin one shouldn't have to install ignore rules to keep an index from crashing ms code.

Same issue here! I don't use any C++ extension... just writing LaTeX document.
Again please: What I have to do to preserve my battery level from falling down at 10% in less than 10 minutes?


Also replace + by space in urlDecode

urlDecode() handles percent-escapes but not converting + to space. In form input the browser should convert space to +, not to %20, and at least Safari indeed seems to do so.

Would you mind adding that little change, or do you have any objections?
I can't do it myself without write permissions to the PR branch.

Done. I've also given you access to my fork so next time feel free to commit such mods yourself (if you want:-).


Spelling error on "az security assessment"

Describe the bug
Two misspellings present of "programmatic" as "progremmatic" on https://learn.microsoft.com/en-us/cli/azure/security/assessment?view=azure-cli-latest#az-security-assessment-create-optional-parameters
Related command
az security assessment create
Errors
n/a
Issue script & Debug output
n/a
Expected behavior
Spelling of programmatic is corrected.
Environment Summary
n/a
Additional context
No response

Thank you for opening this issue, we will look into it.

The code is here:
https://github.com/Azure/azure-cli/blob/a55dcd9bd7fc4b1b82deda8e5334377ce89bf9a0/src/azure-cli/azure/cli/command_modules/security/_params.py#L78-L79
@lewism77, do you mind submitting a PR so that you can get the credit for fixing it? Thanks!

Thanks, I have created a PR


SASS

Hi,
i like your theme! What about SASS source files?
I can help you with this :)

I uses less. I won't change without any special good reason and I don't to provide two versions. Sorry :)


force ssl & HTTP/2 flags not honored in initial creation

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
yes
Are you sure you're not using someone else's docker image?
yes
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
no problems

Describe the bug
When creating a new proxy - the Force SSL / HTTP/2 Support does not get applied initially and requires going back in and setting it after the proxy has been created.  I have an automation script running, so that means another API call.
Input:
{
   "domain_names":[
      "test2.mydomain.com"
   ],
   "forward_scheme":"http",
   "forward_host":"someinternaladdress",
   "forward_port":5555,
   "block_exploits":true,
   "allow_websocket_upgrade":true,
   "access_list_id":"0",
   "certificate_id":"new",
   "ssl_forced":true,
   "http2_support":true,
   "meta":{
<EMAIL_ADDRESS>      "letsencrypt_agree":true
   },
   "advanced_config":"",
   "locations":[

   ],
   "caching_enabled":false,
   "hsts_enabled":false,
   "hsts_subdomains":false
}

JSON fields
   "ssl_forced":true,
   "http2_support":true,

with the resulting response:
{
   "id":22,
   "created_on":"2020-07-20T23:00:12.000Z",
   "modified_on":"2020-07-20T23:00:41.000Z",
   "owner_user_id":1,
   "domain_names":[
      "test2.mydomain.com"
   ],
   "forward_host":"someinternaladdress",
   "forward_port":5555,
   "access_list_id":0,
   "certificate_id":22,
   "ssl_forced":0,
   "caching_enabled":0,
   "block_exploits":1,
   "advanced_config":"",
   "meta":{
<EMAIL_ADDRESS>      "letsencrypt_agree":true,
      "nginx_online":true,
      "nginx_err":null
   },
   "allow_websocket_upgrade":1,
   "http2_support":0,
   "forward_scheme":"http",
   "enabled":1,
   "locations":[

   ],
   "hsts_enabled":0,
   "hsts_subdomains":0,
   "certificate":{
      "owner_user_id":1,
      "provider":"letsencrypt",
      "nice_name":"test2.mydomain.com",
      "domain_names":[
         "test2.mydomain.com"
      ],
      "expires_on":"2020-10-18T22:00:38.000Z",
      "meta":{

      }
   },
   "owner":{
      "is_disabled":0,
      "name":"Admin",
      "nickname":"Admin",
      "avatar":"//www.gravatar.com/avatar/c7a?default=mm"
   },
   "access_list":null,
   "use_default_location":true,
   "ipv6":false
}

JSON Result:
 "ssl_forced":0,
 "http2_support":0,

What version of Nginx Proxy Manager is reported on the login page?
2.3.1

To Reproduce
Steps to reproduce the behavior:
1.) Add Proxy Host

2.) Request New Certificate:

3.)  Result once proxy has been created with cert.

Expected behavior
Expected that the bool values would be applied at initial api post, and not a second call to enable those two flags.
Operating System
-- Ubuntu 20.04 LTS
.

I can confirm this is an issue when creating new proxy hosts, currently on latest version (2.3.1) running on docker (latest) on Debian 10.4.

Same here: Force SSL, HTTP/2 support, HSTS are not saved during new host creation. I need to edit the host to enable these options.
Same problem occurs with redirection hosts.

This bug is critical. It may not, like in my case, be visible to the developer.
My customers report an "unsafe page". The redirection fails.

is there an update to this bug

Same issue..

This is still the case in 2.11.3


Support more than fixing cargo check

Right now cargo fix is hardcoded to always run cargo check. That should catch almost all warnings but it won't catch perhaps super-late codegen-time warnings. It may be worthwhile supporting something like cargo fix test to give the guise of "just put fix in there and all your worries are taken care of!"

I'm gonna close this as this has ended up being sufficient over time.


If the pod is in CrashLoopBackOff, the phase is reported as Running

I have the following scenarion:
➜ k tree klb cd208ccf823b044089c48669c1ec1d6e4
NAMESPACE  NAME                                                                    READY  REASON              AGE
default    KameletBinding/cd208ccf823b044089c48669c1ec1d6e4                        True                       143m
default    └─Integration/cd208ccf823b044089c48669c1ec1d6e4                         False  ReplicaSetNotReady  143m
default      ├─ConfigMap/cd208ccf823b044089c48669c1ec1d6e4-application-properties  -                          143m
default      ├─ConfigMap/cd208ccf823b044089c48669c1ec1d6e4-source-000              -                          143m
default      ├─Deployment/cd208ccf823b044089c48669c1ec1d6e4                        -                          143m
default      │ └─ReplicaSet/cd208ccf823b044089c48669c1ec1d6e4-585565bdf5           -                          143m
default      │   └─Pod/cd208ccf823b044089c48669c1ec1d6e4-585565bdf5-nptc7          False  ContainersNotReady  143m
default      └─IntegrationKit/kit-cd208ccf823b044089c48669c1ec1d6e4                -                          143m

so the POD is not ready for an internal error but the phase of the integration is still reported as Running and the kamelet binding as Ready:
➜ k get klb cd208ccf823b044089c48669c1ec1d6e4
NAME                                PHASE
cd208ccf823b044089c48669c1ec1d6e4   Ready
➜ k get it cd208ccf823b044089c48669c1ec1d6e4
NAME                                PHASE     KIT   REPLICAS
cd208ccf823b044089c48669c1ec1d6e4   Running         1
➜ k get pods | grep cd208ccf823b044089c48669c1ec1d6e4
cd208ccf823b044089c48669c1ec1d6e4-585565bdf5-nptc7   0/1     CrashLoopBackOff   32         141m

I wonder if we can ave a better way to report that the pod is not running.
By looking at the integration resource only, one may mistakenly think the integration is running but it is not.

/cc @astefanutti @nicolaferraro

Additional info:
The Integration has a condition where type=ready and status=false
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
  name: cd208ccf823b044089c48669c1ec1d6e4
status:
  conditions:
  - lastTransitionTime: "2021-06-24T20:49:04Z"
    lastUpdateTime: "2021-06-24T20:49:04Z"
    reason: ReplicaSetNotReady
    status: "False"
    type: Ready
  phase: Running

But the parent KameletBinding, does not reflect such status:
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: cd208ccf823b044089c48669c1ec1d6e4
spec:
status:
  conditions:
  - lastTransitionTime: "2021-06-24T18:07:56Z"
    lastUpdateTime: "2021-06-24T18:07:56Z"
    status: "True"
    type: Ready
  phase: Ready
```

Just yesterday I pushed a change to update integration status related to Deployment status, which in this case the kameletbinding and integration sets the Phase as Error.
$ k get it,klb,pods
NAME                                                  PHASE   KIT                        REPLICAS
integration.camel.apache.org/mongodb-source-binding   Error   kit-c3ahd39gvo520gho5ge0   1

NAME                                                     PHASE
kameletbinding.camel.apache.org/mongodb-source-binding   Error

NAME                                          READY   STATUS             RESTARTS   AGE
pod/camel-k-operator-5f55d8b4c5-95kqk         1/1     Running            2          23h
pod/mongodb-server-7f65f49f79-vq2k2           1/1     Running            12         8d
pod/mongodb-source-binding-5647f6c7dd-77kd9   0/1     CrashLoopBackOff   6          8m58s

Can you try with a recent camel-k-operator build ?

It should be fixed with #2682, available in 1.7.0.


Remove FTX from the codebase

Before submitting this PR, please make sure:

[ ] Your code builds clean without any errors or warnings
[ ] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:
Remove FTX connector from the codebase as it's not more usable.
Tests performed by the developer:
Tips for QA testing:
Run any strategy

latest commit [50af3b4](https://github.com/hummingbot/hummingbot/pull/5893/commits/50af3b4a51fc43f1afae4db94bb756cf8514227c)

Test performed:

Installation tests for client

source build successful
built docker image successfully

Source Build:

Setup client and created password successfully
ftx was removed from the list of connectors (on connect command) successfully
Called connect ftx to verify to be invalid choice
Ftx confirmed as invalid entry during testing
Failed to create any strategy with Ftx as connector

Docker build:

There’re errors on docker image

@cardosofede There're errors/warning messages on docker image creation:
Cannot find corresponding config to key ftx ..... in template
Steps:
Clone and install branch
Manually create docker image
run ./create.sh to create new docker instance
Actual:
There're warning message on new docker instance creation
18:37:52 - root - Cannot find corresponding config to key ftx_buy_percent_fee_deducted_from_returns in template.
18:37:52 - root - Cannot find corresponding config to key ftx_maker_fixed_fees in template.
18:37:52 - root - Cannot find corresponding config to key ftx_maker_percent_fee in template.
18:37:52 - root - Cannot find corresponding config to key ftx_percent_fee_token in template.
18:37:52 - root - Cannot find corresponding config to key ftx_taker_fixed_fees in template.
18:37:52 - root - Cannot find corresponding config to key ftx_taker_percent_fee in template.


Doesn't work in NodeJS

Got a window is undefined error, which suggests it was written for browser environments.
webpack://colorutil/webpack/universalModuleDefinition:10
})(window, function() {
   ^
ReferenceError: window is not defined
    at Object.<anonymous> (webpack://colorutil/webpack/universalModuleDefinition:10:4)
    at Module._compile (node:internal/modules/cjs/loader:1159:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
    at Object.require.extensions.<computed> [as .js] (/root/.local/share/pnpm/global/5/.pnpm/ts-node@10.9.1_@types+node@20.2.3_typescript@5.0.4/node_modules/ts-node/src/index.ts:1608:43)
    at Module.load (node:internal/modules/cjs/loader:1037:32)
    at Function.Module._load (node:internal/modules/cjs/loader:878:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:169:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:530:24)

I was just coming here to open this issue. Thanks @alexkreidler.
For anyone else coming here with this problem, version 2.2.1 does not have this issue and works in NodeJS.


get_tree().paused , yield() still continues in for loop

Godot version:
3.2
OS/device including version:
Windows 10
Issue description:
Yield does not pause at get_tree().paused
Steps to reproduce:
You can paste this code under a NODE2D extends:
extends Node2D

var x = load("res://icon.png")
var t = Timer.new()
func _ready():
	t.one_shot = true
	self.add_child(t)
	t.start(1)

func emit():
	for each in 100:
		var sprite : Sprite = Sprite.new()
		sprite.texture = x
		sprite.position = Vector2(rand_range(0, 1000), rand_range(0, 1000))
		self.add_child(sprite)
		yield(get_tree().create_timer(0.2), "timeout")

func _process(delta):
	print(t.time_left)
	if t.is_stopped():
		emit()
		get_tree().paused = true

Minimal reproduction project:
see code above

Pause only stops _process() from being called and yield continues on an existing call. Not sure if yield even has necessary context to make stopping it possible.

Simply pass false as second argument to create_timer and the timer created will not process during pause.
yield(get_tree().create_timer(0.2, false), "timeout")

@shafnaz Simply pass false as second argument to create_timer and the timer created will not process during pause.
yield(get_tree().create_timer(0.2, false), "timeout")

@Faless That works very well indeed! Thank you!
I suppose I should close this issue. What do you guys think?

Well, if it's only about the timer, then the issue can be closed.

@shafnaz Simply pass false as second argument to create_timer and the timer created will not process during pause. yield(get_tree().create_timer(0.2, false), "timeout")

It's a shame that I overlooked that second parameter 😄  thanks for reminding me of it. 👍


MolFromSmiles failure causes memory leak/double free

Description:
There appears to be a double free() in MolFromSmiles if the underlying topology is in error, as with "C1C1". In an older version of RDKit, there is no double free, but there is a memory leak.
I tested this under 2018.03.4, 2019_03_3, and git HEAD as of 22 July 2019.

RDKit Version:  '2019.09.1dev1'
Platform: macOS Mojave 10.14.4

In RDKit-2019_03_3 and git HEAD, MolFromSmiles("C1CC1") causes a free() error, saying "pointer being freed was not allocated".
>>> from rdkit import Chem
>>> Chem.MolFromSmiles("C1C1")
[11:16:02]

****
Pre-condition Violation
bond already exists
Violation occurred on line 386 in file /Users/dalke/cvses/rdkit/Code/GraphMol/ROMol.cpp
Failed Expression: !(boost::edge(bond_pin->getBeginAtomIdx(), bond_pin->getEndAtomIdx(), d_graph) .second)
****

python(16524,0x112cec5c0) malloc: *** error for object 0x7fef7b890298: pointer being freed was not allocated
python(16524,0x112cec5c0) malloc: *** set a breakpoint in malloc_error_break to debug
Abort

In RDKit-2018.03.4 it correctly gives the "Pre-condition Violation" (just like the newer versions) but it does not have the double free. Instead, it has a memory leak.
I assume the change causing the above was part of trying to fix that leak, but that's only a guess.
The reproducible is:
from rdkit import Chem
Chem.MolFromSmiles("C1C1")

I can't reproduce this behavior on my linux box. @adalke: you're running on a Mac, right?

Yes, running macOS Mojave 10.14.4, "Apple LLVM version 10.0.1 (clang-1<IP_ADDRESS>)". I only built these versions this morning when trying to get a more recent build for the report.
If you don't get the crash, can you reproduce the memory leak?
from rdkit import Chem
while 1:
  Chem.MolFromSmiles("C1C1")

should show increasing memory use.
When I run the following using the Anaconda build of 2018.03.4:
import psutil
from rdkit import Chem
process= psutil.Process()
Chem.MolFromSmiles("C1C1")
start_rss = process.memory_info().rss
num_calls = 0
for i in range(1000):
  num_calls += 1
  Chem.MolFromSmiles("C1C1")

rss = process.memory_info().rss - start_rss
print("leaks", rss/num_calls, "bytes/call")

I get "Violation occurred on line 356 in file /Users/glandrum/anaconda5/conda-bld/rdkit_1534389448433/work/Code/GraphMol/ROMol.cpp" and "leaks 1400.832 bytes/call"

I believe there is a leak, but I can’t reproduce the crash.  I’m going to run valgrind shortly.

Brian Kelley

On Jul 22, 2019, at 10:14 AM, Andrew Dalke<EMAIL_ADDRESS>wrote:
Yes, running macOS Mojave 10.14.4, "Apple LLVM version 10.0.1 (clang-1<IP_ADDRESS>)". I only built these versions this morning when trying to get a more recent build for the report.
If you don't get the crash, can you reproduce the memory leak?
from rdkit import Chem
while 1:
Chem.MolFromSmiles("C1C1")
should show increasing memory use.
When I run the following using the Anaconda build of 2018.03.4:
import psutil
from rdkit import Chem
process= psutil.Process()
Chem.MolFromSmiles("C1C1")
start_rss = process.memory_info().rss
num_calls = 0
for i in range(1000):
num_calls += 1
Chem.MolFromSmiles("C1C1")
rss = process.memory_info().rss - start_rss
print("leaks", rss/num_calls, "bytes/call")
I get "Violation occurred on line 356 in file /Users/glandrum/anaconda5/conda-bld/rdkit_1534389448433/work/Code/GraphMol/ROMol.cpp" and "leaks 1400.832 bytes/call"
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi @bp-kelley  and @greglandrum ,
I'm having the same issue in RDKit version 2020.03.3, installed with conda-forge (since the default conda installation gave me an old version from 2018 that didn't have inchi keys).
Since this issue is closed, is there a version I can install that doesn't have the memory leak?
Thanks a lot!

@mgarort which operating system are you using?

Hi @greglandrum , thanks for your quick response. I'm on Ubuntu 18.
I'm currently investigating and I've realized that the issue is indeed a memory leak but it's not exactly the same as the one reported by @bp-kelley , so I'm investigating further to see where it's coming from. I am using Chem.MolFromSmiles and Chem.MolToSmiles within pandas.DataSeries.map(), and I'm also filling in the argument canonical  for Chem.MolToSmiles with functools.partial.
I will investigate more and come back with a minimal example where the memory leak happens.

Hi @greglandrum ,
I've created another issue with a detailed explanation of my (potential) memory leak, since it seems to be different from the one in this issue. Thanks!


variables with multiple values.

In yaml, there is the posibility to define keys with multiple values, and when you load the file you get an array of values for that key.
for example:
proxies:
  - proxy-one.proxy.com
  - proxy-two.proxy.com

if I load this file using YAML.load, I'll get what I expect. But if I  put it in application.yml, I get the first value only.
is this a bug or intentional behavior?

I have the same doubt

to solve my problem I setted:
proxies: "proxy1;proxy2"
and called the split method
ENV['proxies'].split(";")
please, let me know if there is a better way!

The README.md mentions this deficiency. ENV is only capable of storing string keys and values. It's a basic limitation of ENV. You'd have to split them at runtime, as mentioned by @jampow. Thank you!


Fix crash after Swift 3 migration (Any size)

unsafeBitCast assumes that any Any is of size 32 so it asserts when trying to unsafeBitCast CFHost which comes as an Any. The workaround is cast it to AnyObject before unsafeBitCast.

👍


Drivers grab instrument name from removed _name attribute

With the most recent version of qcodes the definition of Instrument._name is removed. However, all of the connect methods in the different ZI drivers use this attribute to grab the instrument name (rather than Instrument.name). This now leads to an AttributeError as it does not exist. These calls to self._name should all be replaced by self.name.

Thanks, sounds good!

@NicoHendrickx thanks for raising this issue
@jenshnielsen thanks for the heads up and the PR
Currently we are refactoring zhinst-toolkit and zhinst-qcodes anyway (#26) It will be merged probably end of this week and be released as version 0.3.
The refactored zhinst-qcodes does no longer need the private attribute _name


Codacy "Expressions don't expand in single quotes"

Signed-off-by: Patrick Hession<EMAIL_ADDRESS>Describe your changes in brief
Changes

Use double quotes to make sure expressions expand.

How Has This Been Tested? (Optional)

[ ] Please describe in detail how you tested your changes.
[ ] Include details of your testing environment, and the tests you ran to
[ ] How your change affects other areas of the code, etc.

Screenshots (if appropriate)
Checklist

[ ] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

duplicate file


(PUP-11232) Add frozen_string_literal to lower memory consumption

After changes from f8827f83cbbe316e0399b76f2e42f6411e532729, memory consumption of puppet/lib drops from 150653689 to 135704679.
With 932d2f630a6b071639a142788f86bd666d6f596b, memory consumption of puppet/lib drops even further to 135338732. This is achieved by adding frozen_string_literal: true in lib/puppet/pops/model/factory.rb and lib/puppet/pops/types/type_formatter.rb and calling dup method on strings that need to be modified during a run.
305be0d17f21080b736cc179bf2d277b6ade366b simply removes freeze method calls on Strings in lib/puppet/pops/parser/lexer2.rb since frozen_string_literal: true makes them unnecessary and aligns some code columns.

jenkins please test this on all

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

jenkins please test this on all

@joshcooper, I've created PUP-11236 for lexer2 investigation and I've also added 2 more commits here. Please let us know if 932d2f630a6b071639a142788f86bd666d6f596b especially raises any concerns 😄

jenkins please test this with servertests


lshw: B.02.18 -> 02.19

Description of changes

Bump version
Switch to fetchFromGitHub to get updates from @r-ryantm bot
Remove patches (they're merged upstream)
Update dependencies
Fix version workaround (not necessary anymore)
Add myself as maintainer
Fix the version for repology.org (see commit message for details)

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg eval


New version: astral-sh.ruff version 0.1.14

- [X] Have you signed the Contributor License Agreement?

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.5 schema?

Microsoft Reviewers: Open in CodeFlow

Manual Validation ended with:

8:16:50 AM: 2024-01-24 08:16:49.880 [FAIL] Installer failed security check. Url: https://github.com/astral-sh/ruff/releases/download/v0.1.14/ruff-0.1.14-x86_64-pc-windows-msvc.zip Result: 0x80004005

(Automated response - build 629.)

Hi @Trenly,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 629.)

Hi @Trenly,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 656.)

Automatic Validation ended with:

Installation failed with exit code -1978335187 2024-01-25 12:45:10.850 [FAIL] Installer failed security check. Url: https://github.com/astral-sh/ruff/releases/download/v0.1.14/ruff-0.1.14-i686-pc-windows-msvc.zip Result: 0x80004005 MSI (s) (00:64) [12:44:55:971]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Minimum Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. MSI (s) (00:E0) [12:44:57:002]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Additional Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. [1AAC:1BBC][2024-01-25T12:44:54]w363: Could not create system restore point, error: 0x80070422. Continuing...

(Automated response - build 656.)

Hi @Trenly,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 656.)

Automatic Validation ended with:

Installation failed with exit code -1978335187 2024-01-25 12:45:10.850 [FAIL] Installer failed security check. Url: https://github.com/astral-sh/ruff/releases/download/v0.1.14/ruff-0.1.14-i686-pc-windows-msvc.zip Result: 0x80004005 MSI (s) (00:64) [12:44:55:971]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Minimum Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. MSI (s) (00:E0) [12:44:57:002]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Additional Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. [1AAC:1BBC][2024-01-25T12:44:54]w363: Could not create system restore point, error: 0x80070422. Continuing...

(Automated response - build 656.)

This package has failed a Defender scan twice. Should we keep rescanning?

This package has failed a Defender scan twice. Should we keep rescanning?

Lets give it a few more days before trying one final scan

Hi @Trenly,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 679.)

Automatic Validation ended with:

Installation failed with exit code -1978335187 2024-01-25 12:45:10.850 [FAIL] Installer failed security check. Url: https://github.com/astral-sh/ruff/releases/download/v0.1.14/ruff-0.1.14-i686-pc-windows-msvc.zip Result: 0x80004005 MSI (s) (00:64) [12:44:55:971]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Minimum Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. MSI (s) (00:E0) [12:44:57:002]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Additional Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. [1AAC:1BBC][2024-01-25T12:44:54]w363: Could not create system restore point, error: 0x80070422. Continuing...

(Automated response - build 679.)

Hi @Trenly,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 679.)

Automatic Validation ended with:

Installation failed with exit code -1978335187 2024-01-25 12:45:10.850 [FAIL] Installer failed security check. Url: https://github.com/astral-sh/ruff/releases/download/v0.1.14/ruff-0.1.14-i686-pc-windows-msvc.zip Result: 0x80004005 MSI (s) (00:64) [12:44:55:971]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Minimum Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. MSI (s) (00:E0) [12:44:57:002]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Additional Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. [1AAC:1BBC][2024-01-25T12:44:54]w363: Could not create system restore point, error: 0x80070422. Continuing...

(Automated response - build 679.)

/AzurePipelines run

Hi @Trenly,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 695.)

Automatic Validation ended with:

Installation failed with exit code -1978335187 2024-01-30 13:41:54.060 [FAIL] Installer failed security check. Url: https://github.com/astral-sh/ruff/releases/download/v0.1.14/ruff-0.1.14-x86_64-pc-windows-msvc.zip Result: 0x80004005 MSI (s) (74:9C) [13:41:35:934]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X64 Minimum Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. MSI (s) (74:FC) [13:41:36:887]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X64 Additional Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. [14A4:0374][2024-01-30T13:41:33]w363: Could not create system restore point, error: 0x80070422. Continuing... 2024-01-30 16:22:36.968 [FAIL] Installer failed security check. Url: https://github.com/astral-sh/ruff/releases/download/v0.1.14/ruff-0.1.14-i686-pc-windows-msvc.zip Result: 0x80004005 MSI (s) (C0:38) [16:22:22:483]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Minimum Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. MSI (s) (C0:30) [16:22:23:483]: Windows Installer installed the product. Product Name: Microsoft Visual C++ 2022 X86 Additional Runtime - 14.38.33130. Product Version: 14.38.33130. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0. [061C:04CC][2024-01-30T16:22:20]w363: Could not create system restore point, error: 0x80070422. Continuing...

(Automated response - build 695.)

/AzurePipelines run

Manual Validation ended with:

2:44:39 PM:
2024-02-02 14:44:37.720 [FAIL] Installer failed security check. Url: https://github.com/astral-sh/ruff/releases/download/v0.1.14/ruff-0.1.14-x86_64-pc-windows-msvc.zip Result: 0x80004005

(Automated response - build 695.)

Hi @Trenly,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 695.)

/AzurePipelines run

/AzurePipelines run

Automatic Validation ended with:

No errors to post.

(Automated response - build 707.)

@wingetbot waivers Add Validation-Executable-Error

/AzurePipelines run


crashes on quilt because fabricId cannot be null

The mod seems to be incompatible on quilt due to it passing null here as quilt doesn't accept that could you fix this?

I know that quilt compatibility is not provided now due to it still being in beta (#32), but this seems very easy to fix. This +1-1 patch works for me:
diff --git a/Fabric/src/main/java/com/lowdragmc/shimmer/fabric/client/ShimmerModClient.java b/Fabric/src/main/java/com/lowdragmc/shimmer/fabric/client/ShimmerModClient.java
index 666b305..96cec88 100644
--- a/Fabric/src/main/java/com/lowdragmc/shimmer/fabric/client/ShimmerModClient.java
+++ b/Fabric/src/main/java/com/lowdragmc/shimmer/fabric/client/ShimmerModClient.java
@@ -182,7 +182,7 @@ public class ShimmerModClient implements ClientModInitializer, SimpleSynchronous

     @Override
     public ResourceLocation getFabricId() {
-        return null;
+        return new ResourceLocation("shimmer");
     }

     @Override

If the maintainer(s?) would like me to open a PR for this please let me know.

can someone please get me a 1.19.2 version with this patch, I have just spent the last 1.5 hours trying to patch it myself with no experience in java, jar files, compiling or decompiling.

is there a download for a 1.20.1 quilt version of the patch?


Add Stacey Potter as Project Member

GitHub Username: staceypotter

[X] I have reviewed the community membership guidelines in community-roles.md
[X] I have subscribed to the cncf-flux-dev e-mail list https://lists.cncf.io/g/cncf-flux-dev/join
[X] I am actively contributing to 1 or more fluxcd GitHub org repos (eg. Flux, Flagger)
[X] I have enabled 2FA in GitHub
[X] I have two sponsors that meet the sponsor requirements listed in the community membership guidelines
[X] I have spoken to my sponsors ahead of this application, and they have agreed to sponsor my application

Sponsors (please reply):

@dholbach
@makkes

List of contributions to the Flux project:
https://github.com/fluxcd/website/pulls?q=is%3Apr+author%3Astaceypotter

+1000000 Stacey for all reasons mentioned above and more

I am very happy to recommend Stacey for Flux project membership and I think this recognition is long overdue 🎉

Hello @fluxcd/org-admins, would you mind adding @staceypotter to the https://github.com/fluxcd org, please?

@dholbach the role definition says project members have "Triage role on all fluxcd GitHub org repos". What do you think is the most efficient way to accomplish that? I don't have permission to do that as core maintainer (at least not on all repos). Is that also something the org-admins would do?

"Triage role on all fluxcd GitHub org repos"

is definitely not something we have consistently applied across all project members in the past. We should find a way to do better in the future but, right now I'm nearly sure we don't have an efficient way to grant triage role across all the repos.
If we do have a way I'm just not aware of, then we should consider following up with an audit of the whole project member list to add triage role to everyone who governance says should already have this. (That's a separate issue...)

I don't honestly know. I believe the bit about triage permissions stemmed from earlier revisions of our governance.
I'll defer to the

core maintainers if this is sensible to keep (I would say so to make interaction easier and have folks help organise bug reports, etc)
org admins on how to most easily implement this - I have no idea

I added this to next meeting's agenda so we don't lose track.

I propose we delete the Triage team and give everyone who is an org member this role. We need all the help we can get with issue/pr labeling.

All done, Stacey is now an org member part of the Triage team 🎉


flexget and thexem - hammering/no id/etc

Please see: https://github.com/Flexget/Flexget/issues/839

Until this issue is resolved we''re removing this plugin from our Wiki page

Whoa, that's pretty crazy. Looking at your posts, none of those are IPs of the two systems I administer. Likely someone with an otherwise faulty modified configuration.
Regardless, it looks like some simple caching in the plugin will help a lot, even with those improper configs. I'm currently on vacation, but I'll look into this as soon as I can.

@jawilson my config was one of the offending configs... I don't know if I
am working from an older version of the plugin than you were but, I thought
I had copied your config (or at least the references to thexem) to the
letter. If you have a chance would you mind looking at my config or
pointing me to instructions to update non standard plugins.
On Sun, Jan 31, 2016, 02:50 Jeff Wilson<EMAIL_ADDRESS>wrote:

Whoa, that's pretty crazy. Looking at your posts, none of those are IPs of
the two systems I administer. Likely someone with an otherwise faulty
modified configuration.
Regardless, it looks like some simple caching in the plugin will help a
lot, even with those improper configs. I'm currently on vacation, but I'll
look into this as soon as I can.
—
Reply to this email directly or view it on GitHub
https://github.com/jawilson/dotfiles/issues/5#issuecomment-177428278.

@thezoggy I'm going to try and work on this tonight.

Thanks!
-----Original Message-----
From: "Jeff Wilson"<EMAIL_ADDRESS>Sent: 2/21/2016 3:56 PM
To: "jawilson/dotfiles"<EMAIL_ADDRESS>Cc: "thezoggy"<EMAIL_ADDRESS>Subject: Re: [dotfiles] flexget and thexem - hammering/no id/etc (#5)
@thezoggy I'm going to try and work on this tonight.

Reply to this email directly or view it on GitHub:
https://github.com/jawilson/dotfiles/issues/5#issuecomment-186926346

@thezoggy I've had a limited time to work on updating the plugin, I still plan to get it updated to be more sane, just need time to do it.
In the meantime, I think you probably ended up banning my IP (<IP_ADDRESS>) as I can't access the site from home. I've removed TheXEM from my config (see cd5cc43). However, I can't test my plugin changes on my development installation while my IP is banned, so could you please unblock my IP if it is indeed being ignored? Thanks, and I'm really sorry for the issues.

yep ip was banned, it is now unbanned

I haven't had time to update my thexem plugin, I just stopped watching the shows that were a problem. I've also moved my flexget config to https://github.com/jawilson/flexget-config, so this is no longer an issue.


new release

@mwild1 what would be required for a new release?
What I've noticed;

[x] links in the documentation need updating [done, see #7]
[x] this repo has release 1.2.0 and 1.3.0 (tags), yet README.md has 1.4.0... In the mailing list was mentioned 1.4.0 was to be released soon (tm) [done, see discussion below and #7]
[x] LuaRocks has release 1.3.3 as latest  [done, see discussion below]
[ ] Ownership of LuaRocks is with @tomasguisasola currently. Should that stay?
[x] are there differences between @tomasguisasola released 1.3.3 and the current repo, that might break user expectations?  [done, see discussion below and #7]
[x] Document the totable.lua module, done in pr #10, waits for merge
[ ] PR #3
[ ] Do we keep the ancient VC6 files around? PR #12
[ ] chaining calls; PR #15
[ ] XmlDecl bugfix; PR #16
[ ] additional handlers implemented; Pr #17

Any other concerns or things that need fixing/updating?
EDIT: updated status on the items listed

The next planned release is 1.4.0. Most of the changes in this version are aiming to consolidate the differences between Tomás's repo and mine - so people using versions from my repo (most Linux distros) or from Tomás's (mostly LuaRocks) should be equally unaffected by the new release.
I don't really mind who handles the LuaRocks uploads, as long as everyone is using the same code :)
From my perspective I've only been waiting for the two things - approval from Tomás that the new code covers all the functionality specific to his branch (it was not a trivial merge), and... just time :)

I don't want to hold back the new release.  Versions 1.3.3 and 1.3.2 that I released were just small adjustments to make the library compatible to Lua 5.X (there were no 5.4 at that time) and LuaJIT (2.0 and 2.1).  There were no new features at all.
I am not sure if the ownership of LuaRocks is an issue at all, but I can speak to Hisham and ask him to change, if you prefer.  I have just updated the homepage at LuaRocks to:
https://lunarmodules.github.io/luaexpat/
If I can help to anything else, feel free to ask me.

Within Lunarmodules we've been discussing setting up a Lunarmodules luarocks account. So to automate releases. A new tag on the master branch would then automatically generate a new rock on luarocks. @alerque did some work on that. This might be a good time to revive that.

Sure, I can help get it rolling. I wasn't quite ready to tag a luachcheck release which is where that discussion was happening I think, but I think we pretty much agreed on the gist of how it could work and it shouldn't be too hard to implement. I have the CI pieces in another project I think.

Looks like the relevant discussion and the beginnings of my implementation were here:
https://github.com/lunarmodules/luacheck/pull/26

If I can help to anything else, feel free to ask me.

@tomasguisasola one thing would be to document the totable.lua module (I added it as an item to the original post at the top, also updated with other stuff)

@tomasguisasola @mwild1 how can we get a new release moving?
The open PRs #15, #16, #17 are pretty straight forward I think and easy to review, commit-by-commit, #3 is also simple, but arbitrary. And then there is #3 which is probably most work to review.

in the above post I mentioned #3 twice, obviously that should have been #12. Where #12 is the easy but arbitrary one (removing VC6 files), and #3 is the more complex change (threats).
Anyway; the first 3 have been approved and merged. Leaves those 2, before releasing. Reviews appreciated.

As for release process, I have a GitHub Actions workflow I've been iterating on in another repository that's working pretty well to publish tagged releases using an API key in a repository secret. Just needs a little tweaking for the workflow(s) we've talked about in LunarModules.

A new tag on the master branch would then automatically generate a new rock on luarocks. @alerque did some work on that. This might be a good time to revive that.

That work is done. See this issue for some of the choices to make when setting this up. I'm happy to PR it to this repo if whoever is doing release management makes some of those preference decisions.

Bare semver tags like 1.2.3 or prefixed like v1.2.3 (my preference).

Bare is traditional for this repo, so let's keep with that.

Dev rockspec in root or elsewhere? Named dev or scm?

We have: https://github.com/lunarmodules/luaexpat/blob/master/luaexpat-dev-1.rockspec

Upload rockspecs on any file change, or only a tag matches the rockspec version?

I'm not sure I fully understand this question, but... sounds like requiring a tag would be my preference? I prefer tags as a source of truth.

Upload rockspecs only on change, or any time a tag is pushed?

Same as above.

Require all rockspecs pass tests before uploading any of them, or upload those that pass?

I'm okay with uploading those that pass tests.

Test build old rockspecs if touched?

Maybe?

Upload from patch release branches or only the default branch?

Upload from release branches is fine if tagged.
Hope this helps! Thanks for your work on putting this together.

@mwild1 Great, I think that covers most questions.
The only one left is whether to add the workflows for the above directly to this repo or stick them in a common org repo (and hence be able to update them without touching every repo use a very brief include syntax to call them). I'm strongly leaning towards the latter option at least for the 3 repos I'm involved in release management for but there is no reason this repo would have to follow suit.
Would you prefer to have a full copy of the workflow (with the above preferences hard coded) in this repo or reference an external one passing those decisions in as options?

I'm fine with a central repo. It's not like we can't change later if for some reason there is a need. :+1:

Alright then time for me to whip up a PR I guess.

Did you guys decide what to do with the LuaRocks module ownership? No sweat either way, but if you want to use the lunarmodules user we can (and we'll have an org level secret set for that), otherwise whoever manages the user being used on the Lua Rocks side will need to create an API key and then add said key to the secrets settings for this repository as LUAROCKS_APIKEY.

I think let's go with 'lunarmodules' as uploader if nobody objects to that.

I am not sure if I have to do something else regarding LuaRocks module ownership but I agree with the change to lunarmodules user.  I am busy now to dedicate time on this project, but I want to help with anything I can.

FYI @alerque I merged the release PR, but didn't tag it yet, as I expected you to want to do this through the automation

@Tieske Yes I noticed, see also this comment.


Nweather managed serviceaccount support (#4)

Signed-off-by: Nathan Weatherly<EMAIL_ADDRESS>
moved charts to always and toggle directories
fixed unit tests
add managed serviceaccount support with unit tests

https://github.com/stolostron/backlog/issues/19265

/lgtm

/hold
Waiting to validate discovery migration is completed before merge

/lgtm
Please post upstream SNAPSHOT that you validated your changes in in our team channel after merge.

/unhold

Snapshot: https://github.com/stolostron/backplane-pipeline/commit/9e31f965319ff932fbde5cea6c5ef8f9bfca5254
2022-02-14-21-30-26


Broken with rand_core 0.6.1

It seems rand_core 0.6.1 breaks this lib
Here is my usage and then the error I get
use rand_core::OsRng;
let local_diffie_secret = EphemeralSecret::new(OsRng);

error[E0277]: the trait bound `OsRng: rand_core::RngCore` is not satisfied
   --> src\main.rs:406:49
    |
406 |     let local_diffie_secret = EphemeralSecret::new(OsRng);
    |                                                    ^^^^^ the trait `rand_core::RngCore` is not implemented for `OsRng`
    |
   ::: C:\Users\laptopuser\.cargo\registry\src\github.com-1ecc6299db9ec823\x25519-dalek-1.1.0\src\x25519.rs:76:19
    |
76  |     pub fn new<T: RngCore + CryptoRng>(mut csprng: T) -> Self {
    |                   ------- required by this bound in `EphemeralSecret::new`

error[E0277]: the trait bound `OsRng: rand_core::CryptoRng` is not satisfied
   --> src\main.rs:406:49
    |
406 |     let local_diffie_secret = EphemeralSecret::new(OsRng);
    |                                                    ^^^^^ the trait `rand_core::CryptoRng` is not implemented for `OsRng`

Windows 10 20H2 19042.746

rustup 1.23.1 (3df2264a9 2020-11-30)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.49.0 (e1884a8e3 2020-12-29)`

[dependencies.x25519-dalek]
version = "1.1.0"

[dependencies]
rand = "0.8.3"
rand_core = "0.6.1"

------# Full dependencies
[dependencies]
sciter-rs = "0.5.53"
libc = "0.2"
lazy_static = "1.4"

serde = { version = "1.0.117", features = ["derive", "rc"] }
serde_json = "1.0.59"
rand = "0.8.3"
rand_core = "0.6.1"
aes-gcm = { version = "0.8.0", features = ["heapless"]}
ring = "0.16.5"
base64 = "0.13.0"

[dependencies.x25519-dalek]
version = "1.1.0"

Hi! Thanks for alerting us to this. We're not supporting rand 0.6 yet, but we plan to in an upcoming 2.x-alpha release. (cf. PR #64)


Currency conversion not working properly

Thank you for your great plug in! I really like it a lot!
There is a bug:
I enter:
NASDAQ/AAPL(1)[EUR]
result: 161€
but the real value is currently $161 not 161€
The EUR value is 145,35 € (which is not displayed)
conclusion: currency conversion is not working properly, instead the dollar value is displayed.

Did you try „NASDAQ/AAPL(1)[USD]“ ?

Thank you for that hint. I did try that and it displays a better value, closer to the correct on in EURs.
I don't understand. Isn't it now supposed to be displayed in USD? Is the currency conversion taken care of properly?
I like to see AAPL traded in USD and the value displayed in MoneyMoney in EUR. So your syntax is the right one for that?

The program logic is converting everything to be displayed in EUR (as standard).
Since EODData unfortunately does not tell you the source currency of the ticker, I added the currency bracket feature.
(See missing currency info e.g. in http://eoddata.com/stockquote/NASDAQ/AAPL.htm)
Afterwards the extension is converting from source currency X to EUR, which is displayed in MoneyMoney. The conversion is also done with the EODData (see http://eoddata.com/stockquote/FOREX/EURUSD.htm).
Therefore the displayed value refers to the last end-of-day info from the stock market and from FOREX. Additionally, there might be little rounding errors depending on the FOREX data precision.
Happy to hear that you enjoy the extension. Is there anything I can improve from your perspective?

This is great news! Thanks for clarifying/explaining how your wonderful lua-plug in works.
A great "feature" would be the ability to add stock with buying date and then having the development of the stock in perspective. Gain/loss from buying day. Also restocking stock would be nice, like buying more stock from the same company and having that shown in the list.
btw: you can close the ticket, since the issue is resolved. Thank you!

Well, I think you can do most of this already today.

If you do a right click on the stock in MoneyMoney, you can add a purchasing price and gains/losses are displayed accordingly. I'm not loading historical data. But if you update MM regularly, you will have the history here.
If you further add stock, you can either add this as an additional ticker (to track it separately) or just update the ticker (lets say 200 shares instead of 100) and update the average purchasing price.

I'm closing the issue. Feel free to let me know in case there is anything I can help you with.


As a user, I want to see price and status of parcel on hover-over of pin on map.

Pointer enabled devices only

and the square feet of the parcel


LeetHub doesn't work at GFG, probably because GFG just updated its UI.  Expected behavior

LeetHub doesn't work at GFG, probably because GFG just updated its UI.

here is the image for referance


Feature: Add "Back to Top" Button on Content-Rich Pages

Feature description

Several content-rich pages like blogs, contributors pages do not have 'back to top' button.

Considering the abundance of content, it is crucial to include a convenient "Back to Top" button on these pages to enhance
user accessibility and ensure smooth scrolling to the page's beginning.
I would like to work on this issue under GSSoc'23. Could you please assign this issue to me.

👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

@VSatwika  Go for it.
For any support join our community: https://codeincommunity.com/

@SauravMukherjee44 Pls assign this task to me. I am a GSSOC contributor


Sourcemaps do not work. Maybe remove "

Hello,
the source maps do not work because the styles are written directly into the head area. It would be nice if you could change this, so we are able to work with sourcemaps.
Thanks in advance,
Burgart

You can prevent that by using the PostCSS plugin. This way the styles don’t have to be rewritten on the client-side and the original <link> tag stays unchanged.

@burgart did it work for you?

Works now with the Sass Mixin.


Spring InitializingBean and Objects.requireNonNull()

I'm tryting to integrate NullAway into a project I've just started, that is using Spring Batch.
There is an idiom, where ItemReader has bunch of setters, and some of them might be required to call (I know, constructor would be nicer, but bear with me). The way they force it is by using org.springframework.beans.factory.InitializingBean
public class MyItemReader<T> extends AbstractItemCountingItemStreamItemReader<T> implements ResourceAwareItemReaderItemStream<T>, InitializingBean
{

    private RawNestedDataMapper<T> itemDataMapper;

    public void setItemDataMapper(final RawNestedDataMapper<T> itemDataMapper)
    {
        this.itemDataMapper = itemDataMapper;
    }

    @Override
    public void afterPropertiesSet() throws Exception
    {
        Objects.requireNonNull(itemDataMapper, "itemDataMapper is required");
    }

    @Nullable
    @Override
    protected T doRead() throws Exception {
        String line = readLine();
        if (line == null) {
            return null;
        }

        try {
            return itemDataMapper.mapLine(line, lineCount);

        } catch (Exception ex) {
            throw new FlatFileParseException(ex.getMessage(), ex);
        }
    }

}

I've read the docs and my understanding and expectation was, that if I mark InitializingBean as initializer
<compilerArgs>
    <arg>-XepOpt:NullAway:KnownInitializers=org.springframework.beans.factory.InitializingBean.afterPropertiesSet</arg>

the NullAway will understand that the afterPropertiesSet is a semi-constructor, that is called before any work is done in the class and therefore can check the requirements (for example that the property is initialized) and I won't have to do the check anywhere else in the class.
But instead, it produces following errors
[ERROR] MyItemReader.java:[153,17] [NullAway] initializer method does not guarantee @NonNull field resource is initialized along all control-flow paths (remember to check for exceptions or early returns).
    (see http://t.uber.com/nullaway )
[ERROR] MyItemReader.java:[155,32] [NullAway] read of @NonNull field itemDataMapper before initialization
    (see http://t.uber.com/nullaway )

If I change the implementation to
    @Override
    public void afterPropertiesSet() throws Exception
    {
        if (itemDataMapper == null) {
            throw new NullPointerException("itemDataMapper is required");
        }
    }

it still prints following error
[ERROR] MyItemReader.java:[153,17] [NullAway] initializer method does not guarantee @NonNull field resource is initialized along all control-flow paths (remember to check for exceptions or early returns).
    (see http://t.uber.com/nullaway )

maven: effective pom
    <plugin>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>3.8.0</version>
        <dependencies>
          <dependency>
            <groupId>org.codehaus.plexus</groupId>
            <artifactId>plexus-compiler-javac-errorprone</artifactId>
            <version>2.8.5</version>
            <scope>compile</scope>
          </dependency>
          <dependency>
            <groupId>com.google.errorprone</groupId>
            <artifactId>error_prone_core</artifactId>
            <version>2.3.3</version>
            <scope>compile</scope>
          </dependency>
        </dependencies>
        <configuration>
          <compilerId>javac-with-errorprone</compilerId>
          <forceJavacCompilerUse>true</forceJavacCompilerUse>
          <source>1.8</source>
          <target>1.8</target>
          <compilerArgs>
            <arg>-Werror</arg>
            <arg>-Xlint:all,-fallthrough,-processing,-serial,-classfile</arg>
            <arg>-parameters</arg>
            <arg>-XDcompilePolicy=simple</arg>
            <arg>-Xep:NullAway:ERROR</arg>
            <arg>-XepOpt:NullAway:AnnotatedPackages=com.cogvio.dl</arg>
            <arg>-XepOpt:NullAway:TreatGeneratedAsUnannotated=true</arg>
            <arg>-XepOpt:NullAway:AcknowledgeRestrictiveAnnotations=true</arg>
            <arg>-XepOpt:NullAway:KnownInitializers=org.springframework.beans.factory.InitializingBean.afterPropertiesSet</arg>
          </compilerArgs>
          <annotationProcessorPaths>
            <path>
              <groupId>org.springframework.boot</groupId>
              <artifactId>spring-boot-configuration-processor</artifactId>
              <version>2.2.0.M1</version>
            </path>
            <path>
              <groupId>org.springframework</groupId>
              <artifactId>spring-context-indexer</artifactId>
              <version>5.2.0.M1</version>
            </path>
            <path>
              <groupId>com.uber.nullaway</groupId>
              <artifactId>nullaway</artifactId>
              <version>0.7.2</version>
            </path>
          </annotationProcessorPaths>
          <showWarnings>true</showWarnings>
          <parameters>true</parameters>
        </configuration>
      </plugin>

Hi @fprochazka , thanks for the detailed report!
This is interesting. It's indeed true that XepOpt:NullAway:KnownInitializers is a way to mark methods as being initializers. However, the expectation is that an initializer method will initialize/set the @NonNull fields that remain un-initialized by the constructor. So NullAway is complaining that afterPropertiesSet doesn't actually initialize/set itemDataMapper.
In NullAway's model, the idea is that the initializer will be called after the constructor but before any other method of the object.
Of course, what is happening here is that the method initializes nothing, it just guarantees that after you call it, everything has been initialized by other methods (namely setItemDataMapper which acts like the actual initializer here, in the NullAway sense).
We could make NullAway check which fields can be null on exit from the initializer, rather than require them to be set inside the initializer. That would work in this case, but there is still a more fundamental issue with that model, namely that NullAway would understand that code as:

The constructor runs first
Then afterPropertiesSet
Then any other method, including  setItemDataMapper

So you could write your code as:
public class MyItemReader<T> extends AbstractItemCountingItemStreamItemReader<T> implements ResourceAwareItemReaderItemStream<T>, InitializingBean
{

    private RawNestedDataMapper<T> itemDataMapper;

    public void setItemDataMapper()
    {
        this.itemDataMapper = itemDataMapper;
        itemDataMapper.foo();  // RUNTIME NPE!!!
    }

    @Override
    public void afterPropertiesSet() throws Exception
    {
        Objects.requireNonNull(itemDataMapper, "itemDataMapper is required");
    }

}

And NullAway would miss the error!
I think what you want is either of these:

Mark the setXXXX method as @Initializer. This might still require NullAway changes if multiple initializer methods are needed.
Have specific logic to handle Spring InitializingBean as a NullAway handler
(The most practical short term): Mark all classes implementing InitializingBean with @SuppressWarnings("NullAway.Init") that still gets you most of the benefits of nullness checking itself, but trusts you to take care of field initialization.

In general (3) would be my starting point for any classes with a complex initialization life-cycle (anything beyond constructor + single initializer method).
Does this all make sense?
cc: @msridhar for thoughts

Thank you for the response, I can see now that it's not that simple to solve.
I had to verify, but it turns out I can mark only the specific field (and not the entire class) with @SuppressWarnings("NullAway.Init"), which is good enough for me :)
I'll leave it up to you if you want to keep this issue open for further discussion, I consider this resolved.

Thanks for the report, @fprochazka.  The only other relevant thing I can think of are external init annotations, but that doesn't apply here since there is no special annotation on these classes (the convention is based on implementing an interface).  Like @lazaroclapp said, if there a strong desire to have built-in support in NullAway for this convention, it could be done with a handler.


drivers: sensor: tsl2591

Add the tsl2591 sensor to drivers.

Hello all, just hoping to get a review on this.

@MaureenHelm @teburd @kartben @fabiobaltieri
I greatly appreciate you all taking the time to review and merge my PR. Thank you again!

@MaureenHelm @teburd @kartben @fabiobaltieri
I greatly appreciate you all taking the time to review and merge my PR. Thank you again!

Great job! Looking forward to reviewing more PRs from you in the future :)


feat(): add file-system provider

Summary

[ ] Bug fix (corrects a fault without impacting current features)

[X] New feature (adds a new functionality without affecting the existing ones)

[ ] Major change (adds or modifies a feature that impacts existing functionalities)

@mdf/file-system-provider: create provider for managing file system operations using fs from Node.js  .

What has changed?

@mdf/file-system-provider: create provider for managing file system operations using fs from Node.js  .

Author's Checklist Before Publication

[X] I have verified that the modification works correctly.
[X] The modification adheres to the standards set by the Mytra Control DevOps group.
[X] The modifications do not include keys, tokens, or confidential information in the pipeline.
[X] Corresponding unit tests have been conducted to cover the new code and/or the tests that are no longer necessary have been removed.

Change the provider nane to: jsonl-file-store
fix the rest of comments

Pull request closed and moved to release branch


2.0: Documentation updates for COSIGN_EXPERIMENTAL and new flags

Description

We need to remove references to COSIGN_EXPERIMENTAL in code (tests and CLI docs), documentation, and blog posts. We also need to update documentation with any new required flags (like identity flags) and optional flags (like tlog-upload).

Timing is a little awkward here. There's a few changes we should have staged up and ready to go simultaneous with the release (anything breaking). Before the 2.0 release we can't push most of these.
Leaving COSIGN_EXPERIMENTAL in for a while doesn't actually hurt anything, and I worry switching too soon will cause confusion before folks have updated.


Add support for Apptainer installation

Problem description
Hello,
I am currently trying to use the nf-flu pipeline with Apptainer (formerly known as Singularity) as the container engine. However, I noticed that the current documentation and configuration do not explicitly mention or support Apptainer.
Given that Apptainer is becoming increasingly popular in scientific computing environments, especially for its enhanced security features and compatibility with HPC systems, I believe adding support for Apptainer would be beneficial for many users.
Thank you for considering this request.
Sincerely,
Yang

Sovled by nextflow run nf-flu -profile test_illumina, conda --max_cpus $(nproc) -with-conda in Apptainer.


Update Nutanix Frame Custom Partition

IGEL Frame Custom Partition changes:

New IGEL CP Profiles to import.

Three profiles to choose from: standard Frame App, Frame App with SAML2 & Kiosk mode, Frame App with SAT & Kiosk mode.
Each profile has optimized IGEL Desktop preferences.
Kiosk Scripts log to /userhome/.frame/log*.log (non-persistent).
Required environment variables for various scenarios are now included with placeholder values.

New Launcher scripts for Kiosk use-cases:

SAML2 Kiosk Launcher

Auto-launches on IGEL start; monitors the app and auto-restarts it if it somehow closes. Always ensures a full-screen UX.

SAT Kiosk Launcher

Simplified environment variables
Script can actively check the current user’s session status via periodic API calls and will automatically kill, wipe the cache, and re-launch Frame App for a tight and secure UX.

Other changes:

Updated Frame App's Icon file (with a transparent background)
Added links to Frame Documentation in the scripts.
Removed ancient screenshots of Frame Dashboard.

Reviewed and merged in.


Exec user process caused: exec format error on Raspberry PI 4

Hello,
I'm trying to run valheim-server on a Raspberry Pi 4. I have installed Ubuntu server 64bit on my PI, installed docker, copied over the world and made sure the paths are correct. However, when attempting to launch the docker container, it immediately exits with very little debug information.

What's going on here? Are there some more detailed logs I can check out to figure out what's going on here?

The explanation is right there: Valheim server is amd64, your host OS is arm64.
As long as there is no arm64 server you will have a hard time getting it to work on your Pi.

The explanation is right there: Valheim server is amd64, your host OS is arm64.
As long as there is no arm64 server you will have a hard time getting it to work on your Pi.

Hmm, that's too bad. Is this related to the CPU architecture or is it related to the OS? I've heard that Windows has a translation layer that can interpret ARM to x86 instructions. Is there any way to do this on a Linux distro?

Both MacOS and Windows for ARM have a fledgling translation layer that can SORTA run x86/64 instructions on ARM-based processors (and Apple is really pushing their M1 so theirs will continue to get better), but as far as I am aware there is no such thing for RPi and, even if there was, the performance hit for emulating x86/64 commands would be too great to sufficiently run a Valheim server.
I'm sorry to say that you're not going to find a workaround to run it on a RPi.  It's possible that the source code for the Valheim server would be released at some point in the future at which point it's possible it will be compiled for ARM and then something like an RPi might be able to handle a low-slot server, but even then I think you would run into performance issues.
Best of luck!


MacOS: FlutterMetalResizableBackingStoreProvider unnecessarily blocking main thread

Right now during every repaint FlutterMetalResizableBackingStoreProvider unconditionally calls [commandBuffer waitUntilScheduled]. This normally takes less than a milliseconds, but desktop being desktop, when there is some other CPU/GPU load present I've seen this spike to up to 5 milliseconds. Blocking platform thread for 5 milliseconds is quite a lot.
Under normal circumstances flipping doesn't need to happen synchronously. So instead of [commandBuffer waitUntilScheduled], [commandBuffer addScheduledHandler:] can be used. The synchronous version is only required during resizing, when everything needs to be done before returning from resize handler.

Actually, the best way to do this would simply be to block in [FlutterResizableBackingStoreProvider resizeSynchronizerFlush:] instead of [FlutterResizableBackingStoreProvider resizeSynchronizerCommit:].


update feature status

Ref https://github.com/GildedHonour/frank_jwt/issues/22

I'm working on adding them


Possibility to recieve RBG-Actions from Razer Synapse, Logi G Lighthub and replay on Aurora Supported Hardware

Hi,
would it be possible to recvieve events generated from Razer Synapse, Logitech G Lighthub and other Controller software and replay it in Aurora?
So it would be possible to use the "Full Spectrum Browsing"-Feature between Synapse and Vivaldi-Browser with another RBG-Keyboard.
cya

I have a Corsair Strafe RGB and was able to get Vivaldi to display various colors on my keyboard by installing the Razer wrapper into the folder that contains vivaldi.exe. In Vivaldi the feature is called "Razer Chroma Theme Integration". Is that what you are looking for?
There is also a Logitech wrapper and I have had success in using it for apps that support Logitech RGB lighting.

yeah, that was it.
"Full Spectrum Browsing" is working well, thanks.


fixes UTF-8 payload problems

( symbols appeared as ??? in inventory updated via host.update for instance if from non ASCII charset).
See also:
http://stackoverflow.com/questions/6227747/android-default-charset-when-sending-http-post-put-problems-with-special-chara#comment43897389_6228377

Thank you very much.


Small addition to the Indexed function

Small addition to the previous PR, Index now takes an optional argument to allow setting the index type.
Sorry, i realized this would make sense to add a few minutes after you merged the previous one.

Hi!
I like this :-)
Could you please add a specific test with the non-default value (like in the example in the doc)? To have all the cases tested.

I have split up the tests and added one for a pymongo.TEXT argument.
To be more compatible with other versions of mongodb it only checks the key value, not the whole index structure.

I have split up the tests and added one for a pymongo.TEXT argument.
To be more compatible with other versions of mongodb it only checks the key value, not the whole index structure.

Perfect. Looks very neat.
I will merge this guy a little later today or tomorrow.


gitit: init at <IP_ADDRESS>

Motivation for this change
The new gitit upstream release has unbroken the tool.
The second commit makes it into a top-level semi-static binary with a reasonable default runtime closure. 140 MB oO
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc @P-E-Meunier

@GrahamcOfBorg build gitit

It remains to note that after this merge gitit will not be build by hydra.

Why wouldn’t it?

Because haskellPackages.gitit has the flag hydraPlatforms = stdenv.lib.platforms.none; set in it's definition in hackage-packages.nix.

I just tried compiling gitit and it does not build:
onfiguring gitit-<IP_ADDRESS>...
CallStack (from HasCallStack):
  die', called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:1022:20 in Cabal-<IP_ADDRESS>:Distribution.Simple.Configure
  configureFinalizedPackage, called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:475:12 in Cabal-<IP_ADDRESS>:Distribution.Simple.Configure
  configure, called at libraries/Cabal/Cabal/Distribution/Simple.hs:625:20 in Cabal-<IP_ADDRESS>:Distribution.Simple
  confHook, called at libraries/Cabal/Cabal/Distribution/Simple/UserHooks.hs:65:5 in Cabal-<IP_ADDRESS>:Distribution.Simple.UserHooks
  configureAction, called at libraries/Cabal/Cabal/Distribution/Simple.hs:180:19 in Cabal-<IP_ADDRESS>:Distribution.Simple
  defaultMainHelper, called at libraries/Cabal/Cabal/Distribution/Simple.hs:116:27 in Cabal-<IP_ADDRESS>:Distribution.Simple
  defaultMain, called at Setup.lhs:3:10 in main:Main
Setup: Encountered missing or private dependencies:
hoauth2 >=1.3.0 && <1.12

builder for '/nix/store/v1ncl30rcavlhcb1qwdczj5f469mbzw1-gitit-<IP_ADDRESS>.drv' failed with exit code 1
~~~

I should mention that this error occurred on haskell-updates, not on master. We'll merge haskell-updates to master soon, though.


After updating to swift 2 menu item freezes app

After updating my project to Swift 2, 1 of 5 items in my menu freezes the entire app when tapped. All the other items still work fine. I cant figure out for the life of me what is wrong.
Playing around with some prints I noticed the code never even reaches the viewDidLoad function of the view controller.
Any ideas?

This was actually related to: http://stackoverflow.com/questions/32699509/ios-swift-2-0-uitextview-freezes-app-depending-on-text
There was a text view in the controller I was trying to present.


chore: Update hypothesis-graphql

Codecov Report

Merging #1499 (112b4c6) into master (e298591) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1499      +/-   ##
==========================================
- Coverage   99.28%   99.19%   -0.09%
==========================================
  Files          91       91
  Lines        6945     6945
  Branches     1225     1225
==========================================
- Hits         6895     6889       -6
- Misses         26       29       +3
- Partials       24       27       +3

Impacted Files
Coverage Δ

src/schemathesis/extra/pytest_plugin.py
95.58% <0.00%> (-4.42%)
:arrow_down:

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 e298591...112b4c6. Read the comment docs.


Looking for help uploading annotation (COCO format, from JSON file) to task using CVAT API

Hello there,
I'm looking for help with accomplishing my goal.
<please excuse me if this is not the best place to post this, if you have recommendations for a better place, just let me know, I will gladly post this in a more ideal place>
my goal:
programmatically upload a set of annotations to a task (already populated with images) using the CVAT API.
additional context:
I've been trying to perform the upload with my annotations stored locally in a JSON file (COCO format) and have not been successful yet. I'm hoping for guidance in the right direction and/or an example of a functioning annotation upload using the CVAT API. Any help would be very much appreciated. Thank you!
Environment details:
-I'm running CVAT from a docker container on my local machine
Things I've been able to successfully do already (via the CVAT API):
-create/delete a project
-create/delete a task
-upload images to a task
-upload labels to a project
Examples of how I have tried to accomplish my main goal
++++ general attempt1: ++++++++++++++++++
annotations_file_path = Path(r"C:\local_path\annotation_file_in_COCO_format.json")
with open(annotations_file_path, "rb") as f:
    annotations_temp = json.load(f)

# convert json to binary
b64_dict = base64.urlsafe_b64encode(json.dumps(annotations_temp).encode()).decode()

# Upload the annotations to the task
response = requests.put(f"{cvat_server}/api/tasks/{task_id}/annotations", headers=headers, data={'annotation_file': b64_dict})
print(response.json())

this results in the following error msg:
{'detail': 'Unsupported media type "application/x-www-form-urlencoded" in request.'}
+++++ general attempt2: (motivated by how I'm uploading images to a task) +++++++
annotations_file_path = Path(r"C:\local_path")
annotation_file_name = "annotation_file_in_COCO_format.json"
full_annotation_path = Path(os.path.join(annotations_file_path, annotation_file_name))
annotations = []
prefix = f'client_files[1]'
with open(full_annotation_path, "rb") as f:
    annotations_temp = json.load(f)
b64_dict = base64.urlsafe_b64encode(json.dumps(annotations_temp).encode()).decode()
current_tuple = (prefix, (annotation_file_name, b64_dict))
annotations.append(current_tuple)
response = requests.put(f'{cvat_server}/api/tasks/{task_id}/annotations', headers=headers, files=annotations)
# response = requests.post(f'{cvat_server}/api/tasks/{task_id}/annotations', headers=headers, files=annotations)
response.json()

when I use requests.put, I get the following return:
{'version': 0, 'tags': [], 'shapes': [], 'tracks': []}
when I use requests.post, I get the following return:
'No such file were uploaded'
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
additional context:
my headers dict looks like this (and functions correctly in the other contexts I've already had success):
{'Authorization': 'Token <token_UUID_goes_here>'}
cvat_server = 'http://localhost:8080'

Hi, the first variant is almost correct. The endpoint description is available here. You need to upload the file in the annotation_file field. If you're uploading a binary file, specify the multipart/form-data encoding, while for text files json can be used. After uploading you need to send requests to the same endpoint, without files, and wait for the 201 status, 202 will be returned during processing. And example test is here.
We recommend using our high-level Python SDK for file uploading and downloading, you can find an example here.

Hi zhiltsov-max,
Thanks for the advice. I was able to get annotations loaded to a task by using the cvat_sdk.
Many thanks! :)

Hi zhiltsov-max,
Thanks for the advice. I was able to get annotations loaded to a task by using the cvat_sdk.
Many thanks! :)

Hi @gd822 would you like to share your solution on using cvat_sdk upload annotation_file to CVAT task
Appreciate it

Hi @stevezkw1998,
I am still in a beta testing stage with the tools and haven't formalized any classes. So far, just learning how to use the CVAT API / SDK. Here is the rough script I came up with:
import cvat_sdk
import cvat_sdk.core
import os
from pathlib import Path
from shared.utils.config import (
    BASE_URL,
    USER_PASS,
    get_method,
    make_api_client,
    patch_method,
    post_method,
)

import requests
import json
import os
import base64
from pathlib import Path

## Set basic session variables
cvat_server = 'http://localhost:8080'
cvat_username = 'insert_username_here' # superuser
cvat_password = 'insert_pass_here'
auth = requests.post(f'{cvat_server}/api/auth/login', json={'username': cvat_username, 'password': cvat_password})
auth_token = auth.json()['key']
headers = {'Authorization': f'Token {auth_token}'}
client = cvat_sdk.make_client('localhost', port='8080', credentials=(cvat_username, os.getenv('cvat_localhost_test_password')))

## make a new project
project_var = client.projects.create({'name': 'test_subset_work'})

## add labels to project
project_id = project_var.id
labels = [
	{'name': 'label_1', 'color': '#FFE4C4', 'type': 'rectangle'},
	{'name': 'label_2', 'color': '#FA8072', 'type': 'rectangle'},
	{'name': 'label_3', 'color': '#F0E68C', 'type': 'rectangle'},
	{'name': 'label_4', 'color': '#98FB98', 'type': 'rectangle'}
]

url = f'{cvat_server}/api/projects/{project_id}'
for iter in range(len(labels)):
	data_temp = {
		'name': labels[iter]['name'],
		'attributes': [],
		'color': labels[iter]['color'],
		'multi_shapes': False,
		'type': labels[iter]['type']
	}
	data_temp2 = {'labels': [data_temp]}
	response = requests.patch(url, headers=headers, json=data_temp2)
	response_json = response.json()

assign_to = 3 # user_id
task_var = client.tasks.create({'name': 'test_sdk_subset_task',
					'mode': 'annotation',
					'assignee_id':assign_to,
					'project_id': project_id})
task_id = task_var.id

## Upload the image(s) to the task
image_path = Path(r'insert_image_path_here')
images_to_upload = os.listdir(image_path)
images = []
for iter in range(len(images_to_upload)):
	# iter = 0
	current_image = images_to_upload[iter]
	full_image_path = Path(os.path.join(image_path, current_image))
	prefix = f'client_files[{iter}]'
	binary_data = open(full_image_path, "rb").read()
	current_tuple = (prefix, (current_image, binary_data))
	images.append(current_tuple)
response = requests.post(f'{cvat_server}/api/tasks/{task_id}/data', headers=headers, data={'image_quality': 100}, files=images)
response.json()

annotations_file_path = Path(r"insert_path_to_annotation_file") # annotation file is stored in COCO format
task_var.import_annotations('COCO 1.0',annotations_file_path)

Thank you @gd822 Appreciate it

Thank you for the script @gd822 , I am searching since days for a solution. However, I am getting an error message when using it:  ModuleNotFoundError: No module named 'config'.
I tried to solve, without success, there is no such module and also nothing in the cvat file structure
Do you have a newer script, that you were successfully able to run? Can you share it? highly appreciated!

Hi, you can find examples for all high-level API functions here in the tests. If you want to upload annotations to an existing task, you can do it this way (a test):
import os
import sys

from cvat_sdk import make_client
from cvat_sdk.core.helpers import DeferredTqdmProgressReporter

with make_client("https://app.cvat.ai", port=443, credentials=("user", "password")) as client:
    # If working within an org, set the org slug:
    # client.organization_slug = ""

    task = client.tasks.retrieve(42)

    task.import_annotations(
        format_name="CVAT 1.1",
        filename=f"some/dir/task-annotations-cvat_for_images.zip",
        pbar=DeferredTqdmProgressReporter()
    )


Fix typo

Github -> GitHub

@changeworld : Thanks for your contribution! The author, @jeffgilb, has been notified to review your proposed change.

Editorial fix verified.


Human-style text message reminders

Write the copy for text message reminders (not urgent).
Max 140 characters (technically 160, but you never know...)

i'm doing research into text messaging capability that the SFPUC would acquire (purchase). i'll create a new issue if this idea comes to fruition and support is needed!


Build fails following README.md

We cannot release with this failure. What am I missing?
go: finding github.com/fsnotify/fsnotify v1.4.9
Build for odimra service/lib dependencies svc-aggregation are Successful !!!!
Build for odimra service/lib dependencies svc-api are Successful !!!!
Build for odimra service/lib dependencies svc-events are Successful !!!!
Build for odimra service/lib dependencies svc-fabrics are Successful !!!!
Build for odimra service/lib dependencies svc-managers are Successful !!!!
Build for odimra service/lib dependencies svc-systems are Successful !!!!
go: finding github.com/satori/uuid v1.2.0
Build for odimra service/lib dependencies svc-task are Successful !!!!
Build for odimra service/lib dependencies svc-update are Successful !!!!
Build for odimra service/lib dependencies svc-events are Successful !!!!
Removing intermediate container 6935cf04a99a
---> e08169cd5a95
Successfully built e08169cd5a95
Successfully tagged odimra_builddep:tst
cd plugin-unmanaged-racks && make build
make[1]: Entering directory '/home/jonas/ODIM/plugin-unmanaged-racks'
CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -a -tags netgo -ldflags '-w -extldflags "-static"' -ldflags "-X main.version=4a510cc-20210125-dirty" -o ../build/plugin-unmanaged-racks/tmp/urp main.go
/bin/sh: 1: go: not found
Makefile:33: recipe for target 'compile' failed
make[1]: *** [compile] Error 127
make[1]: Leaving directory '/home/jonas/ODIM/plugin-unmanaged-racks'
Makefile:35: recipe for target 'urp' failed
make: *** [urp] Error 2

Resolved with PR : #370

Resolved with PR : #370


backport to 2.0 -- traces going to <IP_ADDRESS> address (#1399)

should this one be back ported to 2.0.1?

Possibly. We may decide to not do 2.0.x bugfix releases (treat it as non-LTS... see mailing list discussion).

Ah, I didn't read far enough in the proposal.  I don't think this is critical enough since the bind address can be passed in on the CL.  Won't be hurt if you just close it.

Okay, let's just close it then, since it's easy to mitigate. We can always reopen and backport if really needed, but this keeps the git history slightly cleaner if we don't need the commit in the history twice.


Sample Code

Near the top of this article, it says View or Download Sample Code which points to https://github.com/aspnet/AspNetCore.Docs/tree/master/aspnetcore/tutorials/razor-pages/razor-pages-start/2.2-stage-samples.  None of these projects, as far as I can see contain code that illustrates CORS talked about in this article.  Am I missing something?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 59bca5db-1196-2a8b-a0d8-4e89b2382288
Version Independent ID: d3f332c4-4c60-039e-0e1e-bc6b11831f87
Content: Enable Cross-Origin Requests (CORS) in ASP.NET Core
Content Source: aspnetcore/security/cors.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@rswetnam  thanks for bringing this to our attention. The link should go to https://github.com/aspnet/AspNetCore.Docs/tree/master/aspnetcore/security/cors/sample

Any chance you could PR this? At the top right of the article, select the Edit pen icon:

Select the pen icon again. Save.


Feature/save id od boundary points

Following discussion in Issues https://github.com/WCSim/WCSim/issues/369, we will save extra trajectory information for OD study.
Logic is as follows:
Check pre-step and post-step volume names and save trajectory points whenever crossing ID blacksheet or OD tyvek.
These trajectory points are saved within WCSimRootTrack class and can be accessed with functions GetBoundaryPoints, etc. Usage are demonstrated in sample-root-scripts/sample_readfile.C
For example, for a muon travelling downward from ID to OD, these trajectory points are saved
Pos -5.25971 6.10425 -32875.5  KE 1829.99 Time 2.92452 Type 1 // ID-blacksheet boundary
Pos -5.47037 6.29294 -32895.5  KE 1824.9 Time 2.99134 Type 1 // blacksheet-deadspace boundary
Pos -14.6706 11.4114 -33475  KE 1712.68 Time 4.92775 Type 2 // deadspace-inner tyvek boundary
Pos -14.6868 11.4162 -33476  KE 1712.6 Time 4.9311 Type 2 // inner tyvek-OD boundary
Pos -63.8851 34.7864 -35497  KE 1297.24 Time 11.6899 Type 3 // OD-outer tyvek boundary
Pos -63.9199 34.7951 -35498  KE 1297.19 Time 11.6932 Type 3 // outer tyvek-outside world boundary

Looks great and all passed. Thanks @kmtsui


Slider control broken

SmallChange property is ignored.

If you have more than 1 slider on a page, the second 1 wont work...

can be reproduced by placing 2 sliders and binding a textbox to each #slider.Value.

I have a PR that hopefully fixes this issue.

@wdcossey yes that fixes the issue thanks


Switch to importlib.resources to load package resources

currently we're using pkg_resources to load resource files like the default.conf. Since Python 3.7, there is the importlib.resources module in the standard library, which provides a more convenient and efficient way to access resources.
Only problem is that we're currently compatible with Python 3.6; should we make >=3.7 a requirement or leave this for now? The benefit is not huge, but support for Python 3.6 will end this year anyway.
We can probably replace the current implementation with
from importlib.abc import Traversable
from importlib.resources import files

def get_resource_string(path: str) -> str:
    """
    Load a package resource (i.e. a file from within this package)

    :param path: the path, starting at the root of the current module (e.g. 'res/default.conf').
           must be a string, not a Path object!
    :return: the contents of the resource file as string
    """
    return get_resource_path(path).read_text()

def get_resource_bytes(path: str) -> bytes:
    """
    Load a package resource (i.e. a file from within this package)

    :param path: the path, starting at the root of the current module (e.g. 'res/image.png').
           must be a string, not a Path object!
    :return: the contents of the resource file as bytes
    """
    return get_resource_path(path).read_bytes()

def get_resource_path(path: Union[str, Traversable]) -> Traversable:
    """Get a reference to a package internal path object"""
    module_name = __name__.split('.')[0]
    return files(module_name).joinpath(path)

I just noticed that importlib.resources.files is only available in Python >=3.9 and the functions available since 3.7, well they suck. So I think we can keep pkg_resources until Python 3.9 becomes the min version for at-python-template...