VSCode uses too much RAM upon Updating to latest version (1.20.1)

VSCode Version: 1.20.1
OS Version: Windows 10

Steps to Reproduce:

Open VSCode on Windows 10
Open task manager :

Does this issue occur when all extensions are disabled?: Yes/No
Yes, because it still uses at around 500mb:

I remembered it uses much less memory than that prior to updating...

Without more details I will close this issue, unless you can pinpoint this to a specific thing you are doing...
Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

I'm not doing anything to be honest, I opened my project with VSCode (An Angular app), edited some code,  then I noticed the editor being unresponsive most of the time that's when I decided to open task manager and saw it uses a lot of memory...

@wtubog ok so the editor getting unresponsive when editing files is not normal and might be unrelated to the memory consumption. When this happens again, can you run "code --status" and attach the output?

Collecting CPU and memory information. This might take a couple of seconds.
Version:          Code 1.20.1 (f88bbf9137d24d36d968ea6b2911786bfe103002, 2018-02-13T15:34:36.336Z)
OS Version:       Windows_NT x64 10.0.16299
CPUs:             Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1800)
Memory (System):  7.86GB (3.78GB free)
VM:               0%
Screen Reader:    no
Process Argv:     C:\Program Files\Microsoft VS Code\Code.exe .
CPU %   Mem MB     PID  Process
0       79   16828  code main
0       66    7564     shared-process
0      118    7612     gpu-process
0      217   11940     window (header.component.ts - vetfo - Visual Studio Code)
0       30    6484       terminal
0        6    9808         winpty-process
0        9   10152           console-window-host (Windows internal process)
0        5   17184           "C:\Program Files\Git\bin\bash.exe"
0        9    2520             "C:\Program Files\Git\bin..\usr\bin\bash.exe"
0       72    6824       extensionHost
0      162    8304         electron_node electronForkStart.js tsserver.js
0       35   14580           electron_node typingsInstaller.js tsserver.js typesMap.js
0       39   11752         electron_node jsonServerMain.js
0      235   15224         electron_node server.js
0       12    7232       electron-crash-reporter
0       33   11832       searchService
0       13   15080       watcherService
0        9   14048         console-window-host (Windows internal process)
Workspace Stats:
|  Window (header.component.ts - vetfo - Visual Studio Code)
|    Folder (vetfo): 112 files
|      File types: ts(31) css(20) json(11) html(10) svg(6) js(6) txt(5) png(3)
|                  eot(3) ttf(3)
|      Conf files: package.json(1) tsconfig.json(1) tslint.json(1)

This is the output when I run code with --disable-extensions (event though I disabled the extensions, VSCode still takes a lot memory):
Collecting CPU and memory information. This might take a couple of seconds.
Version:          Code 1.20.1 (f88bbf9137d24d36d968ea6b2911786bfe103002, 2018-02-13T15:34:36.336Z)
OS Version:       Windows_NT x64 10.0.16299
CPUs:             Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1800)
Memory (System):  7.86GB (3.85GB free)
VM:               0%
Screen Reader:    no
Process Argv:     C:\Program Files\Microsoft VS Code\Code.exe . --disable-extensions
CPU %   Mem MB     PID  Process
0       83    1476  code main
3       78    8180     shared-process
0      123    9572     gpu-process
0      295   12360     window (header.component.ts - vetfo - Visual Studio Code)
0       13    3196       watcherService
0       10    8432         console-window-host (Windows internal process)
0       12    9764       electron-crash-reporter
0       56   14128       extensionHost
0        5    9628         "C:\Program Files\Git\cmd\git.exe" fetch
0       10    7636           console-window-host (Windows internal process)
0        5   15548           git.exe fetch
0        5   11928             git remote-https origin https://github.com/wtubog/vfo.git
0       11    6480               git-remote-https origin https://github.com/wtubog/vfo.git
0        6    8012                 sh -c "git credential-manager get" "git credential-manager get"
0        5    1956                   "C:\Program Files\Git\mingw64\libexec\git-core\git.exe" credential-manager get
0       26    4260                     git-credential-manager get
0      165   10472         electron_node electronForkStart.js tsserver.js
0       35    7744           electron_node typingsInstaller.js tsserver.js typesMap.js
0       39   16976         electron_node jsonServerMain.js
0       31   17176       terminal
0        6    9760         winpty-process
0       10    8452           console-window-host (Windows internal process)
0        5   11996           "C:\Program Files\Git\bin\bash.exe"
0       10   16768             "C:\Program Files\Git\bin..\usr\bin\bash.exe"
Workspace Stats:
|  Window (header.component.ts - vetfo - Visual Studio Code)
|    Folder (vetfo): 112 files
|      File types: ts(31) css(20) json(11) html(10) svg(6) js(6) txt(5) png(3)
|                  eot(3) ttf(3)
|      Conf files: package.json(1) tsconfig.json(1) tslint.json(1)

@wtubog a screenshot of it would help reading the output

Thanks, I am not seeing an outlier here, seems legit so far.

@wtubog does it freeze when you open a particular file?

Yes it does, freezes for about 1 or 2 seconds...

@wtubog for all files or only JS files?

I have exactly same issue with golang project and watcherService taking 100% of CPU and constantly raising memory usage over time.

Getting same issue with VsCode 1.20.1
My memory consumption rise upto 2.5 gb when ts compiles to js, using gulp-typescript. And normally in idle mode its about 1.5 - 1.8 Gb. High memory consumption also impairs intellisense and type support.
Attaching output from code --status:
Collecting CPU and memory information. This might take a couple of seconds.
Version:          Code 1.20.1 (f88bbf9137d24d36d968ea6b2911786bfe103002, 2018-02-13T15:34:36.336Z)
OS Version:       Windows_NT x64 10.0.16299
CPUs:             Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz (4 x 2394)
Memory (System):  7.92GB (2.61GB free)
VM:               50%
Screen Reader:    no
Process Argv:     C:\Program Files\Microsoft VS Code\Code.exe G:\Projects\Test\express-typescript-sequelize\server
CPU %   Mem MB     PID  Process
3       76    5016  code main
0       22    2420     gpu-process
9      142    7716     window (user.dao.ts - server - Visual Studio Code)
0       21    4724       terminal
0        5     540         winpty-process
0        7    9248           console-window-host (Windows internal process)
0       48   10444           C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
0        4   10644             C:\WINDOWS\system32\cmd.exe /c ""C:\Program Files\nodejs\npm.cmd" run build"
0       44    5544       extensionHost
0       23    9308         electron_node tslintServer.js
0       44   10904         electron_node jsonServerMain.js
32     2108   11056         electron_node electronForkStart.js tsserver.js
0       33   14300           electron_node typingsInstaller.js
0       12    8860       watcherService
0        5    6948         console-window-host (Windows internal process)
0       11   11864       electron-crash-reporter
0       32   12864       terminal
0        6    6672         winpty-process
0       61    1648           C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
0        4   11924             C:\WINDOWS\system32\cmd.exe /c ""C:\Program Files\Microsoft VS Code\bin\code.cmd" --status"
0       32    9264               electron_node cli.js
0       50   13444                 "C:\Program Files\Microsoft VS Code\Code.exe" --status
0       30   13492                   gpu-process
1       70   14096                   powershell.exe -NoProfile -ExecutionPolicy Bypass -Command "& {& 'c:\Program Files\Microsoft VS Code\resources\app\out\vs\base\node\ps-win.ps1' -ProcessName 'Code.exe' -MaxSamples 3}"
0        7   11296                     console-window-host (Windows internal process)
0        9   14196           console-window-host (Windows internal process)
0       49    9532     shared-process
Workspace Stats:
|  Window (user.dao.ts - server - Visual Studio Code)
|    Folder (server): 40 files
|      File types: ts(22) js(7) json(6) gitignore(1) sequelizerc(1) md(1)
|                  yaml(1)
|      Conf files: launch.json(1) settings.json(1) gulp.js(1) package.json(1)
|                  tsconfig.json(1)

same issue memory consumption is at 2.6GB for vscode, im building and running a react app

same issue with VsCode 1.22.1

Attaching output from code --status：

Getting same behavior with 1.22.2. At the beginning of the day, fresh start, its using 233Mb. Yesterday at around noon and after noon for some reason I had to restart the app multiple times it was reaching a 2Gb of memory usage. Only had a few ansible files open, and files are not super large. My extensions were all active though. Will test again today.

I'm getting the same behavior with Visual Studio Code 1.22.2
It seems to happen around the time when I resize the built-in terminal.
VSCode going haywire:

Here's the performance meter before/after killing the process.

Yes, It is consuming too much memory

Yes, It is consuming too much memory

All extensions disabled 1.22.2 is eating 800mb to a gig at idle for me. Is that normal? Could well be as I've only just started using Code so I'm not being sarcastic just genuinely curious as this is unusable on my admittedly badly resourced PC. Just seems high fora gloried text editor :(

I switched to emacs and I am loving it.

This is turning into a deal breaker,  freezes my vm, ram just goes ballistic, vs code team do this: open vs code and let it run for 8h straight and see how it  gobbles up

Still happening, Insider version eats upto 1gb of ram without doing much, I hardly use any plugins and It makes a lot of threads when it starts up and that's not how I/O should be done as Ryan Dahl said.

VS Code is too slow and consuming too much memory, I gave up and go back to Sublime/VIM.

this my first post ever on here ....i thot i had to find out what going on....i got an update notification so i updated it ...it has slowed down a lot and i was not doing much just html/css stuff...checked task manager it was sucking up 700mb ..was never like this before update.    ....kinda sucks was working really smooth before update ...hope it get figured out...i do like vs code a lot....just checked memory usage ...having vs code just open is piling it up over 400mb of mem...ouch.

Same issue, about 3 or 4 Code Helper processes are running on mac and taking 1gb memory each

I have build 1.23.1 running on Ubuntu 18.04 and have the same issue as everyone else here ... huge RAM usage, in my case 1.5GB. When I run code --status, I see the culprit is extensionHost. Running without extensions seems to make the problem go away, but of course I NEED those extensions.
If I run for more than an hour or two my entire system will freeze and I'll have to reboot.
This is a real problem, needless to say.

@bpasero any debug traces we can do to help?

The best is to verify the memory consumption is high due to an extension and then disable extensions one by one to find the offender. Then, file a bug against the extension with steps if possible.

We do not have any extra extension installed, the VS CODE is eating a lot memory, apparently it's mainly because the .net behind.

This was in my way so I dug in, and the offending extension seems to be "Import Cost" from Wix. I had it installed as part of the vscode for node.js development pack. Had a lot of extensions and of course it was almost the LAST one I tried. Doh!
Can anyone confirm?

For those of you still experiencing problems, I recommend you see whether it is an extension that is causing the problem, because if so you're not going to see any relief waiting for a bug fix from the core vscode updates. Check your output of  code --status (see posts above) and see if there are multiple processes for extensionHost, one of which is huge.
In my case uninstalling the "Import Cost" extension that is part of the popular vscode for node.js development pack fixed the problem, and I have been running well for 5 days now. I have reported the problem to the maintainers of Import Cost, btw.
If that doesn't help, the problem may be the file watching and indexing. Does the RAM usage get really bad when you first open a project, but then settles down after a few minutes? There is a user/workspace setting called files.watcherExclude that has helped me in the past. Read up on that setting.
Good luck!

For me, it's git. I've done a lot of changes [over 5k], and VSCode's in-built git uses 600-700 MB of memory when it's running in background. I'm really, really frustrated.

I had same problem (explosive RAM/CPU usage) too on Fedora 26, but throwing all big folders (vendor, tmp, dist, etc.) in our project to "files.watcherExclude" solved it (for now).

Come on. Stop pointing fingers to extensions. Even with no extension installed, this thing is a resource hog. Like any Electron based application. Even with a rather small typescript/react projecct + the default typescript extensions (a first party extension dare I say), the thing takes a full CPU core doing nothing, and reaches 2.1GB of memory usage in a minute. I just have to open the application, and boom, time to eat memory.
Looks like something is hammering the garbage collector, because every minute and a half or so, the memory usage drops back to 150MB and rises up again.
This is completely insane.

can you guys share your user / workspace settings that helped you?

Linux 3.10.0-693.el7.x86_64 (CentOS)
VSCode spent all RAM and gave next text in console:
[Error - 09:19:36] Request textDocument/codeAction failed. Error: Connection got disposed. 	at Object.dispose (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/main.js:825:25) 	at Object.dispose (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/client.js:57:35) 	at LanguageClient.handleConnectionClosed (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/client.js:1864:38) 	at LanguageClient.handleConnectionClosed (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/main.js:106:15) 	at closeHandler (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/client.js:1852:18) 	at CallbackList.invoke (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:71:39) 	at Emitter.fire (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:135:36) 	at closeHandler (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/main.js:221:26) 	at CallbackList.invoke (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:71:39) 	at Emitter.fire (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:135:36) 	at StreamMessageReader.AbstractMessageReader.fireClose (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/messageReader.js:135:27) 	at Socket.<anonymous> (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/messageReader.js:188:62) 	at emitOne (events.js:101:20) 	at Socket.emit (events.js:191:7) 	at Pipe._handle.close [as _onclose] (net.js:510:12) [Error - 09:19:36] Request textDocument/codeAction failed. Error: Connection got disposed. 	at Object.dispose (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/main.js:825:25) 	at Object.dispose (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/client.js:57:35) 	at LanguageClient.handleConnectionClosed (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/client.js:1864:38) 	at LanguageClient.handleConnectionClosed (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/main.js:106:15) 	at closeHandler (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/client.js:1852:18) 	at CallbackList.invoke (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:71:39) 	at Emitter.fire (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:135:36) 	at closeHandler (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/main.js:221:26) 	at CallbackList.invoke (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:71:39) 	at Emitter.fire (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:135:36) 	at StreamMessageReader.AbstractMessageReader.fireClose (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/messageReader.js:135:27) 	at Socket.<anonymous> (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/messageReader.js:188:62) 	at emitOne (events.js:101:20) 	at Socket.emit (events.js:191:7) 	at Pipe._handle.close [as _onclose] (net.js:510:12) [Error - 09:19:36] Request textDocument/codeAction failed. Error: Connection got disposed. 	at Object.dispose (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/main.js:825:25) 	at Object.dispose (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/client.js:57:35) 	at LanguageClient.handleConnectionClosed (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/client.js:1864:38) 	at LanguageClient.handleConnectionClosed (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/main.js:106:15) 	at closeHandler (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/client.js:1852:18) 	at CallbackList.invoke (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:71:39) 	at Emitter.fire (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:135:36) 	at closeHandler (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/main.js:221:26) 	at CallbackList.invoke (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:71:39) 	at Emitter.fire (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:135:36) 	at StreamMessageReader.AbstractMessageReader.fireClose (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/messageReader.js:135:27) 	at Socket.<anonymous> (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/messageReader.js:188:62) 	at emitOne (events.js:101:20) 	at Socket.emit (events.js:191:7) 	at Pipe._handle.close [as _onclose] (net.js:510:12)

Same issue, it suddenly started to consume 14 GB of RAM, cool...

My MacBook Pro has been going up and down like a yoyo the last couple of days. I installed, uninstalled and reinstalled extensions and all sorts with no success!
the above disappoints me but the way in which @bpasero was replying to the initial chap who opened this issue annoyed me even more. I mean is it me or is he just being short / rude until everyone else who has this issue starts chipping in?
in the market for a new text editor for creating react applications if anyone has any suggestions?

I actually downloaded Atom for when this happens again, it stopped for now, without me doing anything

after last updates, i saw new bug:
vscode stuck about 5 minutes and after this gave output:
[Error - 10:57:05] Request textDocument/codeAction failed. Error: Connection got disposed. 	at Object.dispose (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/main.js:825:25) 	at Object.dispose (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/client.js:57:35) 	at LanguageClient.handleConnectionClosed (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/client.js:1864:38) 	at LanguageClient.handleConnectionClosed (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/main.js:106:15) 	at closeHandler (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-languageclient/lib/client.js:1852:18) 	at CallbackList.invoke (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:71:39) 	at Emitter.fire (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:135:36) 	at closeHandler (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/main.js:221:26) 	at CallbackList.invoke (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:71:39) 	at Emitter.fire (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/events.js:135:36) 	at StreamMessageWriter.AbstractMessageWriter.fireClose (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/messageWriter.js:57:27) 	at Socket.<anonymous> (/home/pokat/.vscode/extensions/ms-vscode.cpptools-0.17.6/node_modules/vscode-jsonrpc/lib/messageWriter.js:79:63) 	at emitOne (events.js:96:13) 	at Socket.emit (events.js:191:7) 	at Pipe._handle.close [as _onclose] (net.js:510:12)

When I open my PHP project(Yii2 framework) in win10, it takes up too much memory.

Same here

Thanks @billybarnum, it seems, Import Cost extension is memory hungry.
Cheers

I removed all my extensions and it still caused problems, randomly.

I think there are bugs with the integrated console, for me it goes nuts when I run a command to some custom test with some custom test framework inside the integrated terminal.  When I open a separate terminal it doesn't do this, just in VS randomly. This is so sad, VS and  VS Code were the only Microsoft software that ran very well, now that's gone too. RIP

Am running VS code 1.2.5 on Ubuntu 16.04 and everything seems to be okay here. Just open a Laravel application. I don't have very many extensions just Vetur for vue files, Laravel blade snippets with highlighting by Winnie lin and php namespace resolver.
Here is a screenshot of the memory usage.

The version

Have also open two integrated terminal tabs one running php artisan serve and another running npm run watch

1.25.1 on Win 10 1709 here.  58 enabled extensions.  added
"/*/": true
to files.watcherExclude.
Freshly opened with no files in editor, I'm sitting at around  400M idle.
With a simple text file open and the user settings tab open, i'm at 445M.
Open up a  .ps1 file and the command prompt opens up, 750M
Close all open files console stays open until manually killed to recover 100M.
Overall, not horrible for my use case.  Better than the *other electron based editor, but still really heavy.

Mine consume 3gb+ of memory any solution?

Same for me with the latest update on mac code helper get around 2gb of memory

Hello Guys, i was have the problem and after search here, i think the problem is installing a big number of extensions.
After i deleted unnecessary VS Code become faster  and consume less RAM

Same Problem here, originally used Code because it was light. Guess it is time to switch....

Had the same problem, had to disable CSS Peek extension

Hitting high memory issues even without any enabled extension, and finally vscode hangs. Looks like it's related to the integrated terminal in my case.
I'm using 1.25.1, and the simplest repro was:

code --disable-extensions
Open and edit files - everything is fine so far, including RAM.
View -> Integrated Terminal
Type something in the integrated terminal -> RAM spikes to over 1Gb, and vscode isn't responsive anymore.

Thanks!

@boaz-chen that is exactly what I nailed it down to also, if you check my comment above. And I can confirm the flow that you did happens to me too, but not every time. I just pull out the console to do something and puff goes VSCode....

I bet for one dollar that this problem won't be fixed this year.(may even get worse)

I haven't had issues since my previous comment (around 2 weeks)

I download vscode insider and it works fine for now.

Still not fixed. Using up 11GB out of 16 when idle.
Guess it's time to ditch it and move on to Atom or something.

I am also having the same issue and I need extensions too.


Error in Guide: Using Truffle with the Avalanche C-Chain

When working through the guide, after funding, I get this error.
allenharper@Allens-Mac truffle % truffle exec fund-cchain-addresses.js --network development
Using network 'development'.

Exporting 1000 AVAX to each address on the C-Chain...
23xvbLVDTfv73hi7FZfSAA2mEVZiBccMsSBsd5KBM3EQV488Jk
Importing AVAX to the C-Chain...
Please wait
YmTA3qCLiF4nMPRM6L5HQbetQ7znYBuRoSm31Y4yCh8KPZmQ5
allenharper@Allens-Mac truffle % truffle console --network development
truffle(development)> accounts
[
  '0x8db97C7cEcE249c2b98bDC0226Cc4C2A57BF52FC',
  '0x9632a79656af553F58738B0FB750320158495942',
  '0x55ee05dF718f1a5C1441e76190EB1a19eE2C9430',
  '0x4Cf2eD3665F6bFA95cE6A11CFDb7A2EF5FC1C7E4',
  '0x0B891dB1901D4875056896f28B6665083935C7A8',
  '0x01F253bE2EBF0bd64649FA468bF7b95ca933BDe2',
  '0x78A23300E04FB5d5D2820E23cc679738982e1fd5',
  '0x3C7daE394BBf8e9EE1359ad14C1C47003bD06293',
  '0x61e0B3CD93F36847Abbd5d40d6F00a8eC6f3cfFB',
  '0x0Fa8EA536Be85F32724D57A37758761B86416123'
]
truffle(development)> await web3.eth.getBalance(accounts[0]);
'50000001000000000000000000'
truffle(development)> await web3.eth.getBalance(accounts[1]);
'1000000000000000000'
truffle(development)> migrate --network development

Compiling your contracts...
===========================
> Everything is up to date, there is nothing to compile.

Starting migrations...
======================
> Network name:    'development'
> Network id:      43112
> Block gas limit: 8000000 (0x7a1200)

1_initial_migration.js
======================

   Deploying 'Migrations'
   ----------------------

Error:  *** Deployment Failed ***

"Migrations" -- cb is not a function.

    at /usr/local/lib/node_modules/truffle/build/webpack:/packages/deployer/src/deployment.js:365:1
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at Migration._deploy (/usr/local/lib/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:70:1)
    at Migration._load (/usr/local/lib/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:56:1)
    at Migration.run (/usr/local/lib/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:217:1)
    at Object.runMigrations (/usr/local/lib/node_modules/truffle/build/webpack:/packages/migrate/index.js:150:1)
    at Object.runFrom (/usr/local/lib/node_modules/truffle/build/webpack:/packages/migrate/index.js:110:1)
    at Object.run (/usr/local/lib/node_modules/truffle/build/webpack:/packages/migrate/index.js:87:1)
    at runMigrations (/usr/local/lib/node_modules/truffle/build/webpack:/packages/core/lib/commands/migrate/run.js:80:1)
    at Object.module.exports [as run] (/usr/local/lib/node_modules/truffle/build/webpack:/packages/core/lib/commands/migrate/run.js:44:1)
    at Command.run (/usr/local/lib/node_modules/truffle/build/webpack:/packages/core/lib/command.js:189:1)

truffle(development)>

Which guide were you working with?


Settings coming from render process

Tested by making sure the application still runs and uses settings
properly.

unfortunately looks like the solution of moving ./lib from files to resources didn't work. Might work to put it in both though, you could try that


Allow RETURN/STOP in EOF creation tx code

Sibling PR of https://github.com/ipsilon/eof/pull/118. This time we drop the requirement for initcontainer s in EOF creation txs be actually validated to be... "initcontainers", in the sense of not containing RETURN/STOP.
The effect of this is that they can actually RETURN or STOP (without deploying any contract!), in addition to RETURNCONTRACT. So now the creation tx has access to the salt-based hashing scheme, and we also don't care about runtime/initcode mode of such containers.
Opening the PR just to assess the fresh idea in writing, does not mean yet we're changing the spec.

This feels to me more hacky than other variants, because

It requires yet another validation mode, because in other contexts only RETURNCONTRACT or STOP/RETURN are allowed, but not both
RETURN (or STOP) from creation transaction does not result in deployment - this is not consistent with legacy creation transactions (so it's a special case in handling them in Host). Returned data would be just ignored.

it is an error for a container to contain both RETURNCONTRACT and either of RETURN or STOP.

Is this rule still applied?

If we would go with this, it seems kinda logical to also allow STOP/RETURN in EOFCREATE-referenced containers, but I don't think it's a good idea.

To quote @pdobacz from discord discussions

Another way to put this. #119 makes the initcode mode validation a validation of the parent-child relation between containers, not that of the container per se. So top-levelness is irrelevant, containers which have no parent are implicitly not affected by the rule.

I think this is what my original idea was about how validation tests should work in regard to inicode mode validation, but then I realized it's pretty confusing, and better to explicitly validate either initcode mode or runtime mode for toplevel container of validation tests.
And I think similar idea applies to the spec: the spec is more clear and behaviour is better defined if we require specific mode of validation for toplevel container in all contexts where we do validation (so in the spec it is only in creation tx and later possibly TXCREATE).

containers which have no parent are implicitly not affected by the rule.

This exception makes it more complicated to figure out all the rules.

Idea dropped on the EOF impls call (reasons in comments)


Fix PEM PKEY export leak on error path and avoid segfault if PKEY is NULL

These two patches fix

a leak on PEM_write_bio_PrivateKey_traditional error patch (easily detectable with valgrind or address sanitizer).
check if EVP_PKEY is NULL and avoids segfault

Found by this (simplified) testcase:
#include <openssl/bio.h>
#include <openssl/pem.h>
#include <openssl/evp.h>

int main(int arc, char **argv)
{
	EVP_PKEY *pkey = NULL;
	EVP_PKEY_CTX *genctx = NULL;
	BIO *bio = NULL;

	bio = BIO_new_fp(stdout, BIO_NOCLOSE);
	if (!bio) {
		printf("BIO_new_fp failed\n");
		goto out;
	}

	genctx = EVP_PKEY_CTX_new_from_name(NULL, "ED448", NULL);
	if (!genctx) {
		printf("EVP_PKEY_CTX_new_from_name failed\n");
		goto out;
	}

	if (EVP_PKEY_keygen_init(genctx) != 1) {
		printf("EVP_PKEY_keygen_init failed\n");
		goto out;
	}

	if (EVP_PKEY_generate(genctx, &pkey) != 1) {
		printf("EVP_PKEY_generate failed\n");
		goto out;
	}

	/* Check leak in traditional output */
	PEM_write_bio_PrivateKey(bio, pkey, NULL, NULL, 0, 0, NULL);
	PEM_write_bio_PrivateKey_traditional(bio, pkey, NULL, NULL, 0, 0, NULL);

	/* Try pkey = NULL */
	PEM_write_bio_PrivateKey(bio, NULL, NULL, NULL, 0, 0, NULL);
	PEM_write_bio_PrivateKey_traditional(bio, NULL, NULL, NULL, 0, 0, NULL);

out:
	EVP_PKEY_CTX_free(genctx);
	EVP_PKEY_free(pkey);
	BIO_free_all(bio);

	return 0;
}

[x] tests are added or updated

Hm, should I send CLA docs, or this is a trivial change?

Hm, should I send CLA docs, or this is a trivial change?

Please send ICLA and possibly CCLA if this was done as part of an employment. This is outside of CLA: trivial limits.

Hm, should I send CLA docs, or this is a trivial change?

Please send ICLA and possibly CCLA if this was done as part of an employment. This is outside of CLA: trivial limits.

OK, I have already sent it, thanks.

CLA should be solved, I'll close & reopen this PR to clear the flag.

ping for second review

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

Merged to master, 3.1, and 3.0 branches. Thank you for your contribution.


Spelling Fixes - Wave 7

Additional Spelling fixes @Court72

@flang-msft - can you review the changes to articles/azure-cache-for-redis/scripts/create-manage-cache.md
all other edits are confirmed.

#assign: @flang-msft
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks, @flang-msft. I'll merge this PR based on your approval.
If any of the articles require further changes, please open a separate pull request.


SNA on contact

Hello sir @MridulS, please sir I can't figure out why these checks are failing.  Please can you enlighten me more?

It looks like this PR actually includes the changes from #70 as well. It'd be best to split that out - if you're comfortable rebasing/cherry-picking you should be able to drop the commits related to the distance_measures notebook. If not, it's also fine just to git rm the distance measures directory (everything will be squashed at merge time anyways!) LMK if you have any questions!

It looks like this PR actually includes the changes from #70 as well. It'd be best to split that out - if you're comfortable rebasing/cherry-picking you should be able to drop the commits related to the distance_measures notebook. If not, it's also fine just to git rm the distance measures directory (everything will be squashed at merge time anyways!) LMK if you have any questions!

Okay sir, thanks for pointing that out, I am not yet comfortable with rebasing/cherry-picking I'll  try using git rm  instead.  so I think I will leave just https://github.com/networkx/nx-guides/pull/73/commits/a9d21719e3bac9307e5e24d967965b551a9e5970 and https://github.com/networkx/nx-guides/pull/73/commits/3d04e24438eaedf9d7464b1c431e3192697935c8

I'm going to go ahead and close this as it's been stale for a while and still has the "changesets from multiple PRs" issue. @Lukong123 if you're still interested in working on this, the place to start would be to isolate the changes that were intended to be in this PR and push those up. Please feel free to reopen after doing so!


lang: [cs] Add Czech Translation

I have added Czech translation for shield + fixed Slovak translation.

Ok I have reverted Slovak translation with a new commit.

Hi,
Thank you for contributing!
Please see https://github.com/codeigniter4/shield/pull/235#issuecomment-1153050805

@MichalSkoula See https://github.com/codeigniter4/shield/pull/672#issuecomment-1468658726

@MichalSkoula See #672 (comment)

Should I create a new PR?

How to sign past commits is explained here, but feel free to do so if you're comfortable creating new PRs.

Creating a new PR is easier for me. I have done so - https://github.com/codeigniter4/shield/pull/1015


Long names of Cluster (and other) resources cause bootstrapping cluster to fail creation with generic error

What happened:
Attempting to bootstrap an EKS Anywhere cluster using a (very) long name for the  Cluster (and other) resources causes the kind bootstrap cluster to fail creating.
Amongst the plethora of logs, these snippets seem to be most relevant
[apiclient] All control plane components are healthy after 22.003180 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace

...

I0115 20:11:27.767218     147 uploadconfig.go:131] [upload-config] Preserving the CRISocket information for the control-plane node
I0115 20:11:27.767232     147 patchnode.go:31] [patchnode] Uploading the CRI Socket information "unix:///run/containerd/containerd.sock" to the Node API object "diamond-foo22-prod-eksa-mgmt-cluster-eks-a-cluster-control-plane" as an annotation

...

I0115 20:13:27.771568     147 round_trippers.go:553] GET https://diamond-foo22-prod-eksa-mgmt-cluster-eks-a-cluster-control-plane:6443/api/v1/nodes/diamond-foo22-prod-eksa-mgmt-cluster-eks-a-cluster-control-plane?timeout=10s 404 Not Found in 2 milliseconds
I0115 20:13:27.775214     147 round_trippers.go:553] GET https://diamond-foo22-prod-eksa-mgmt-cluster-eks-a-cluster-control-plane:6443/api/v1/nodes/diamond-foo22-prod-eksa-mgmt-cluster-eks-a-cluster-control-plane?timeout=10s 404 Not Found in 2 milliseconds

...

nodes "diamond-foo22-prod-eksa-mgmt-cluster-eks-a-cluster-control-plane" not found
Error writing Crisocket information for the control-plane node

What you expected to happen:
Bootstrap cluster creates successfully.
In the alternative, (and if my guess is correct regarding the character length of the Cluster being the root cause), then some more helpful error message regarding the length of names of (certain) Kubernetes object should be shown. In such a case, it is probably fair to expect  that eksctl anywhere validates the Cluster (and other resources) name length before actually creating the bootstrap cluster.
How to reproduce it (as minimally and precisely as possible):

Try to bootstrap an EKS Anywhere cluster (using almost default configuration) against vSphere Provider (might be reproducable with our providers as well, as the problem manifests itself when creating the KIND bootstrap cluster).
Make sure to use a very long name for the Cluster (and similarly for the other resources, including VSphereMachineConfig, VSphereDatacenterConfig). I used a name with 36 characters.

Renaming the Cluster object down to a more sensible 20-character string (and similarly for  VSphereMachineConfig, VSphereDatacenterConfig resources) fixed the problem.
Anything else we need to know?:

Cluster name (obfuscated, but identical length and character layout): diamond-foo22-prod-eksa-mgmt-cluster
(As evident in the last few lines of the logs shown above), the longe Cluster name caused eksctl anywhere to name the control plane node group diamond-foo22-prod-eksa-mgmt-cluster-eks-a-cluster-control-plane (which is 64 characters in length)

Environment:

EKS Anywhere Release: v0.18.4
EKS Distro Release: bottlerocket-v1.28.4-eks-d-1-28-12-eks-a-56-amd64
Operating System: Fresh Ubuntu 22.04 VM

Note:
I am not entirely sure if this is the correct place to file this bug; but it seemed a good place to start. If the community feels reporting this to kind or kubeadm makes more sense, I'll be happy to do so.

Thanks for reporting @dejarikra! We were able to reproduce the issue on our end as well by setting the EKS-A Cluster resource's name to exactly 36 characters long. On the EKS-A side, we add a suffix -eks-a-cluster to the KinD cluster's name (which makes it 50 characters long) and KinD also adds a -control-plane suffix to the control plane node (container), which makes the control plane node name 64 characters in length.
The interesting part is Kind themselves allow a maximum cluster name length of 50. I tried creating a cluster with 37 characters in length and rightfully hit this warning, followed by a different error when creating the control-plane container which occurs because docker run is invoked with the --hostname parameter which is supplied a 65-character long hostname which doesn't conform to sethostname's 64 character restrictions.
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: sethostname: invalid argument: unknown.

Based on some reading, I reached the conclusion that a maximum of 64 characters is allowed by both Kind and sethostname so the issue may be something in kubeadm or Kubernetes itself. Will dig further and update this issue if I find something.


AMQP-692: Fix MessagingMessageLA missed argument

JIRA: https://jira.spring.io/browse/AMQP-692
Fixes GH-535 (https://github.com/spring-projects/spring-amqp/issues/535)
The ListenerExecutionFailedException does not make sense without a failedMessage.
So, fix MessagingMessageListenerAdapter to use another ListenerExecutionFailedException ctor with the amqpMessage param as a failedMessage arg
Cherry-pick to 1.6.x & 1.7.x
Note: a @Deprecated ctor should be removed for master

Merged as 16eb180a34091501bcf46b02a11ff81352e06fec after cherry-picking and removing ctor.


MAJOR BUG - Camera - App crashes randomly on Android devices

Cf https://github.com/apache/cordova-plugin-camera/issues/665
This issue should be opened back, the crash still happens on most of our clients devices. Can we help you in any way ? Pay you to have a quick fix ?

Is this reproducible in a new, plain Cordova app? A minimal reproduction repository would really help to debug and later fix this issue. More information on how to create one: https://github.com/apache/cordova-contribute/blob/master/create-reproduction.md
And let's stick to the original issue - if you have MRE for us, we are happy to re-open the issue.

@jgoux i think we should create one

@timbru31 instead of closing these issues, can you help us to reproduce the crash ?
Camera is hard to test with desktop emulators, because there's no hardware camera on emulated device. What would be your ideas about it ? Is there a way to simulate hardware camera with desktop computer camera ?

Among all existing issues, the crash seems to occur for devices with a bad CPU / RAM limitations / Camera resolution ratios.
Looks also that different brands manage differently the "limits" of the device.
A basic Re-boot also seems to remove the crash for many devices (but some devices have every time the crash).

=> So to reproduce the error, we should also simulate heavy resolution pictures taken by cameras, and different devices brands.
Thanks for your help !


when a new version planned?

hi @theoephraim
currently there are 11 open pull requests that awaiting a merge.

the current version was released a long time ago.

when is a new version planned to be released?

I've just a published a new version of this module which is a complete rewrite using Google's V4 Sheets API (v3 is being deprecated on March 3, 2020).
Docs available here - https://theoephraim.github.io/node-google-spreadsheet
Thanks! 😄


[Feature Request] el-container content should move to left if el-aside(menu) is collapsed.

Existing Component
Yes
Component Name
el-menu
Description
When El-menu in el-aside is collapsed the content of el-container should move to left.
How can I do this using CSS?

Bind the width of <el-aside> to a variable and update that variable when the Menu collapses / expands.


Lack of supporting graphs

Lack of supporting graphs in the analysis of the trend of agreement in the timeline.

I just look into that, it must be some missing import, I have fixed that and also used colour label for comparison. Thx!


Update the google/generative-ai dependency

I updated the dependency @google/generative-ai because I wanted to use the API version v1beta.
Refs: https://github.com/google-gemini/generative-ai-js/pull/94

Yes merged the earlier PR - will ship a new version shortly!
Thank you!


test: Test node offline scenario in the manager integration test

We want to cover add/remove/node offline in the manager integration test.
As the first step, we want to test https://github.com/longhorn/longhorn-tests/wiki/Manual-Test-Plan#physical-node-down automatically.

Need to add the first reproduce method of #735 in this test case as well.

Moving out to v0.7.0.

Blocked by https://github.com/longhorn/longhorn/issues/909


Feature/session cdr transaction fetch refactor

Adding additional mapping required to map OCPI objects based on Core objects

Dismissing Thana's review for now but will circle back. Merging the PR for now to eliminate build errors with latest 0.2.0 code. We can make additional adjustments in a follow up PR (if needed) 🙇


First time --setup-auto mangling packages.json

Version
5.24.2
Describe the bug
The automation that adds the typesafe-i18n line to scripts in package.json seems to struggle when there are (quoted) closing curly brackets in a previous script entry.
Reproduction
In packages.json:
	"scripts": {
		"prisma:repl": "ts-node --project prisma/tsconfig.json --compilerOptions '{ \"module\": \"node16\" }'"
	},

Then simply:
npx typesafe-i18n --setup-auto

Results in mangled JSON format:
	"scripts": {
		"prisma:repl": "ts-node --project prisma/tsconfig.json --compilerOptions '{ \"module\": \"node16\",
		"typesafe-i18n": "typesafe-i18n" }'"
	},

Logs
Nothing special. All completes succesfully.

Config
Not relevant at this stage.

Additional information
No response

Fixed in version 5.24.3.
Thanks for your help!


Layer Style panel & themes

With a style.theme defined in the configuration that theme will be applied when the layer is loaded. Otherwise the first theme from the style.themes object will be assigned as style.theme.
themes: {} needed to be removed from the defaults to make the themes check falsy if no theme is defined in the layer's style configuration.
Switch all control to be added with corresponding themes not always and then toggled when a theme is applied.
Flatten the layers.view.style directory in lib.
In order to see the 'Basic' theme legend which allows to modify the default style configuration for the layer a theme type: 'basic' needs to be defined.

polyCategorized.mjs and clusterCategorized.mjs have now been merged to categorized.mjs.
The legend should not depend on whether the layer is cluster or mvt format but only whether styles are defined as symbol, line, or polygon.

polyGraduated.mjs and clusterGraduated.mjs have now been merged to graduated.mjs.
The legend should not depend on whether the layer is cluster or mvt format but only whether styles are defined as symbol, line, or polygon.

hyperHTML construction has now been superseeded with microHTML.
Grid element items are now longer in intermediate container but aligned and justified in a grid proper.

The grid theme is now type: grid

The 'basic' type theme can now be configured.
With only the theme type in the configuration this will result in a panel for Stroke (colour, width) and Fill (colour, width).

Individual fields can be defined in a fields array.
Field types can be text or range (for now).
The field name must be provided.
The style can be set to highlight, default is default.
"Basic": {
  "type": "basic",
  "fields": [
    {
      "title": "Color",
      "style": "highlight",
      "type": "text",
      "field": "strokeColor"
    }
  ]
}


Deliver step fails when .ipa file is > 3GB in size. Error: iTMSTransporter could not generate an itmsp: null.

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Increasing ODR content in our app has meant that our .ipa file is > 3GB in size. This has resulted in the deliver step failing. The error we see is
iTMSTransporter could not generate an itmsp: null
The step works fine when the .ipa file is < 3GB in size.
I notice some similar issues raised in the past (https://github.com/fastlane/fastlane/pull/19697), but our version of fastlane (2.204.3) includes the fixes. I don't see a current issue matching ours.
I raised a previous issue for the same problem which can be found here. This issue was closed but the suggested fix did not work for us. We initially reported failures with ipa files > 4GB in size but we've recently seen failures with files 3.2GB in size.
The failure is consistent - it fails every time.
We are able to manually upload our ipa using the Transporter Mac app or the ITMS Cli.
Looking at the docs, we've tried this, in case there were firewall issues - to no avail:
DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS="-t HTTP" fastlane deliver
Command executed
Deliver
+--------------------------------------+-----------------------------------------------+
|                               deliver 2.204.3 Summary                                |
+--------------------------------------+-----------------------------------------------+
| api_key                              | ********                                      |
| team_id                              | **********                                    |
| ipa                                  | RELEASE_ARTEFACTS/Dev-AppStore-ClientNameProduct.ipa |
| automatic_release                    | false                                         |
| app_identifier                       | com.ClientNameProduct.ClientNameProduct                     |
| force                                | true                                          |
| skip_metadata                        | true                                          |
| skip_screenshots                     | true                                          |
| skip_app_version_update              | true                                          |
| precheck_include_in_app_purchases    | false                                         |
| screenshots_path                     | ./fastlane/screenshots                        |
| metadata_path                        | ./fastlane/metadata                           |
| app_version                          | x.xx.x                                        |
| platform                             | ios                                           |
| edit_live                            | false                                         |
| use_live_version                     | false                                         |
| skip_binary_upload                   | false                                         |
| overwrite_screenshots                | false                                         |
| sync_screenshots                     | false                                         |
| submit_for_review                    | false                                         |
| reject_if_possible                   | false                                         |
| phased_release                       | false                                         |
| reset_ratings                        | false                                         |
| run_precheck_before_submit           | true                                          |
| precheck_default_rule_level          | warn                                          |
| ignore_language_directory_validation | false                                         |
+--------------------------------------+-----------------------------------------------+
Complete output when running fastlane, including the stack trace and command used

 + bundle exec fastlane deliver_app_store_build buildType:Dev --env ClientNameProduct
[18:44:51]: Loading from './fastlane/.env.ClientNameProduct'
+--------------------------------------------+---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|                                                                                Used plugins                                                                                |
+--------------------------------------------+---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Plugin                                     | Version | Action                                                                                |
+--------------------------------------------+---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| fastlane-plugin-file_manager               | 0.2.0   | remove_files, copy_files                                                                                |
| fastlane-plugin-lizard                     | 1.3.3   | lizard                                                                                |
| fastlane-plugin-brew                       | 0.1.1   | brew                                                                                |
| fastlane-plugin-ipa_install_plist_generate | 1.0.0   | ipa_install_plist_generate                                                                                |
| fastlane-plugin-json                       | 1.1.0   | write_json, download_json, merge_jsons, read_json                                                                                |
| fastlane-plugin-versioning                 | 0.5.0   | get_version_number_from_git_branch, increment_build_number_in_xcodeproj, get_version_number_from_plist, get_build_number_from_plist, ci_build_number, get_version_number_from_xcodeproj, increment_version_number_in_xcodeproj, increment_version_number_in_plist, get_app_store_version_number, get_info_plist_path, get_build_number_from_xcodeproj, increment_build_number_in_plist |
+--------------------------------------------+---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
18:44:53: --- Step: import_from_git ---
18:44:53: -----------------------------
18:44:53: Cloning remote git repo...
18:44:53: $ git clone git@gitlab.provider.net:back-end-systems/build-pipelines.git /var/folders/sy/47k76vn11dn8tqnpr4369mqc0000gn/T/fl_clone20220311-52639-av55cw/build-pipelines.git --depth 1 --no-checkout
18:44:53: ▸ Cloning into '/var/folders/sy/47k76vn11dn8tqnpr4369mqc0000gn/T/fl_clone20220311-52639-av55cw/build-pipelines.git'...
18:44:53: ▸ ################################################################################
18:44:53: ▸ #                                host.provider.net                               #
18:44:53: ▸ #                  All user logins are monitored and recorded                  #
18:44:53: ▸ #        If you are not a provider authorised user, please disconnect now         #
18:44:53: ▸ ################################################################################
18:44:53: $ cd /var/folders/sy/47k76vn11dn8tqnpr4369mqc0000gn/T/fl_clone20220311-52639-av55cw/build-pipelines.git && git checkout HEAD platform/ios/fastlane/SharedFastfile
18:44:53: ▸ Updated 1 path from 962be67
18:44:53: $ cd /var/folders/sy/47k76vn11dn8tqnpr4369mqc0000gn/T/fl_clone20220311-52639-av55cw/build-pipelines.git && git checkout HEAD platform/ios/fastlane/actions
18:44:53: ▸ error: pathspec 'platform/ios/fastlane/actions' did not match any file(s) known to git
[18:44:54]: ------------------------------
[18:44:54]: --- Step: default_platform ---
[18:44:54]: ------------------------------
[18:44:54]: Driving the lane 'deliver_app_store_build' 🚀
[18:44:54]: --------------------------------
[18:44:54]: --- Step: ensure_bundle_exec ---
[18:44:54]: --------------------------------
[18:44:54]: Using bundled fastlane ✅
[18:44:54]: ---------------------------------------
[18:44:54]: --- Step: app_store_connect_api_key ---
[18:44:54]: ---------------------------------------
[18:44:54]: ---------------------
[18:44:54]: --- Step: deliver ---
[18:44:54]: ---------------------
[18:44:54]: Creating authorization token for App Store Connect API
+--------------------------------------+-----------------------------------------------+
|                               deliver 2.204.3 Summary                                |
+--------------------------------------+-----------------------------------------------+
| api_key                              | ********                                      |
| team_id                              | **********                                    |
| ipa                                  | RELEASE_ARTEFACTS/Dev-AppStore-ClientNameProduct.ipa |
| automatic_release                    | false                                         |
| app_identifier                       | com.ClientNameProduct.ClientNameProduct                     |
| force                                | true                                          |
| skip_metadata                        | true                                          |
| skip_screenshots                     | true                                          |
| skip_app_version_update              | true                                          |
| precheck_include_in_app_purchases    | false                                         |
| screenshots_path                     | ./fastlane/screenshots                        |
| metadata_path                        | ./fastlane/metadata                           |
| app_version                          | 5.17.3                                        |
| platform                             | ios                                           |
| edit_live                            | false                                         |
| use_live_version                     | false                                         |
| skip_binary_upload                   | false                                         |
| overwrite_screenshots                | false                                         |
| sync_screenshots                     | false                                         |
| submit_for_review                    | false                                         |
| reject_if_possible                   | false                                         |
| phased_release                       | false                                         |
| reset_ratings                        | false                                         |
| run_precheck_before_submit           | true                                          |
| precheck_default_rule_level          | warn                                          |
| ignore_language_directory_validation | false                                         |
+--------------------------------------+-----------------------------------------------+
[18:44:58]: Uploading binary to App Store Connect
[18:45:20]: Going to upload updated app to App Store Connect
[18:45:20]: This might take a few minutes. Please don't interrupt the script.
[18:55:27]: Transporter transfer failed.
[18:55:27]:
[18:55:27]: iTMSTransporter could not generate an itmsp: null
An exception has occurred: null
18:55:28: [iTMSTransporter] 	at com.apple.transporter.core.util.TimeLimitedProcess.call(TimeLimitedProcess.java:146)
18:55:28: [iTMSTransporter] 	at com.apple.transporter.core.util.TimeLimitedProcess.call(TimeLimitedProcess.java:25)
18:55:28: [iTMSTransporter] 	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
18:55:28: [iTMSTransporter] 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
18:55:28: [iTMSTransporter] 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
18:55:28: [iTMSTransporter] 	at java.base/java.lang.Thread.run(Unknown Source)
18:55:28: [iTMSTransporter] Error Summary
18:55:28: [iTMSTransporter]     iTMSTransporter could not generate an itmsp: null
18:55:28: [iTMSTransporter]     An exception has occurred: null
18:55:28: [iTMSTransporter] [2022-03-11 18:55:27 GMT]  DBG-X: Returning 1
18:55:28: iTunes Transporter output above ^
18:55:28: iTMSTransporter could not generate an itmsp: null
An exception has occurred: null
Return status of iTunes Transporter was 1: iTMSTransporter could not generate an itmsp: null
\nAn exception has occurred: null
The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.
+------------------+-------------------------+
|                Lane Context                |
+------------------+-------------------------+
| ENVIRONMENT      | ClientNameProduct              |
| DEFAULT_PLATFORM | ios                     |
| PLATFORM_NAME    |                         |
| LANE_NAME        | deliver_app_store_build |
+------------------+-------------------------+
18:55:28: Error uploading ipa file:
+------+---------------------------+-------------+
|                fastlane summary                |
+------+---------------------------+-------------+
| Step | Action                    | Time (in s) |
+------+---------------------------+-------------+
| 1    | default_platform          | 0           |
| 2    | import_from_git           | 1           |
| 3    | ensure_bundle_exec        | 0           |
| 4    | app_store_connect_api_key | 0           |
| 💥   | deliver                   | 633         |
+------+---------------------------+-------------+
18:55:28: fastlane finished with errors
[!]  I've recently updated all of my gems including fastlane and the outcome is exactly the same. We still receive the same ITMS error. Thanks.

Have you managed to overcome this? Happens for me as well

@Mehdzor the issue is still on-going for us.
One avenue that we are investigating is overall time it takes the deliver step to complete. We hypothesise that the Apple api token we are using is going stale before the step has completed. We are investigating if more bandwidth will help.
I'll report back with any findings.

@Kai2k, our app is barely 100Mb, and we experience the same. It happens after binary uploading, and we receive the error almost immediately. It might be something else, but I have no idea.

@Kai2k, our app is barely 100Mb, and we experience the same. It happens after binary uploading, and we receive the error almost immediately. It might be something else, but I have no idea.

we have the same issue with our app

We are still hoping to test increased bandwidth to see if this cures the issue. I'll report back when done, but there may be a wait as it requires some hardware changes.

This is still an issue for us. We are in the process of updating some of our hardware, such as the firewall, to increase bandwidth. Once this is done I'll try a fresh build and report back.

We are still in the process of updating our firewall. I've not forgotten about this and will update if this fixes the issue.

This is still on-going. Our new firewall should be installed within the next 3-4 weeks. I'll post back after this time.

Hello. Unfortunately we still have not been able to update our firewall. I've chased this internally and will post the results asap. Thank you.

Hello again. Good news. This issue is now resolved. The bad news is that I am unsure as to what fixed it. To confirm, we made no specific hardware changes to increase our bandwidth. I can only assume either a Fastlane update, or some back-end update by Apple has resolved this.


Steamworks flat interface overhaul

I've just updated the Steamworks SDK.  Version 1.48 includes a pretty big overhaul to the flat interface, and a new windows-event-like manual callback dispatch mechanism.  The goal is to make binding layers like this easier to write.  Less manual maintenance, and less gross hackery under the hood.
When you get a sec, please take a look at it, and if you have any questions or complaints, email me.

This is pretty exciting to hear :)

Thanks for the work should make things a lot easier. Few things I've noticed so far:

SteamAPI_ISteamNetworking_ReadP2PPacket Still has a CSteamID parameter
CSteamID/CGameID could be helpful to have a way to access the methods of these types when using the raw uint64 versions.
SteamTVRegion_t/ESteamTVRegionBehavior seem to be missing from the headers? They are used in the flat interface and are in the steam_api.json but not the headers.

Thanks!  I'll look into those things and see what I can do.


Fix preview not updating when autosave is off - issue 120

What does this PR do?
This PR address this issue that was introduced in newly published version 50.14.0.  The issue is captured here. https://github.com/forcedotcom/soql-tooling/issues/120
What issues does this PR fix or reference?
https://github.com/forcedotcom/soql-tooling/issues/120

Nice, this looks good. I can't remember why we didn't do it this way before? Also, do we know the source of the bug, when and what changed?

So we used to always show the preview from the soql statement that was generated by the UI.  But then we had that issue where the user could open a soql query from a text editor that we didn't support...but we still wanted to show them the soql statement and allow them to run what they see.  So we switched it to only update the preview from the incoming soql statement.
I think what we want is show the soql statement from the text editor when the change event happens.  But also, when the user interacts with our form, immediately update the soql statement.  Since we are sending that to the text editor anyway.
It's like the best of both worlds now.  I hope.

Nice, this looks good. I can't remember why we didn't do it this way before? Also, do we know the source of the bug, when and what changed?

So we used to always show the preview from the soql statement that was generated by the UI.  But then we had that issue where the user could open a soql query from a text editor that we didn't support...but we still wanted to show them the soql statement and allow them to run what they see.  So we switched it to only update the preview from the incoming soql statement.
I think what we want is show the soql statement from the text editor when the change event happens.  But also, when the user interacts with our form, immediately update the soql statement.  Since we are sending that to the text editor anyway.
It's like the best of both worlds now.  I hope.

QA Passed for me

QA Passed for me


Added "is_" functions (à la ctype.h) as string methods

Added all but one "is_" functions (the exception being isblank())
Updated with the appropriate documentation and comments
Minor code and doc corrections

Thanks! The context parameter of the functions should be a void *, however. It is declared as void *, so it must be void *, doing otherwise results in undefined behavior.
(the reason why it is a void * is that the extra argument can be anything, not only an SpnContext, although this opportunity is not currently used anywhere in Sparkling. In the future, it may even be removed, but for now that's how it is.

I realized that! I initially wrote void*, but found that one of your other aux function accepted a SpnContext; so I figured that the auxiliary functions would accept a SpnContext but the lib functions should rather take the void*.

I shall correct everything, then.

Yes, auxiliary functions (ones that are not directly put into the SpnExtFunc arrays) can (and probably should) accept an SpnContext * argument. They can, since void * is implicitly convertible to any object pointer type. So when you call a function that has a formal parameter of type Foo *, and the call provides an actual parameter of type void *, there's a conversion involved. There's no such conversion, however, when calling a function through a pointer to function of incompatible types (and implicit convertibility alone does not constitute "compatible" in the vocabulary of the C standard), so it simply becomes UB.


Trigger Test-Suite on Pull Requests

It seems that Test-Suite cannot be triggered from pull requests, and thus they cannot be accepted through the proper steps.

I am not sure if this is really needed. I assumed that #103 was not progressing tests because they had not been triggered (hence this PR). But there were some codecov issues that I tried to patch on #106, which may be related or unrelated to the underlying problem.


Additional Event Documentation

For the project I'm working on, I wanted to know, in plain english and at a glance, what each event indicates. I wrote handlers for each event (except signaling) and then went through the OpenTok documentation and copied what I felt were the significant parts into comments above each one. I'm a bit busy at the moment, so I don't have time to add it to the README.md but I figured I'd put it here for others' consideration.
  /* Session Event Handlers */

  // This event happens when this client's session has connected to OpenTok
  onSessionDidConnect (/* sessionId */) {}

  // The client has disconnected from the session. This event may be dispatched asynchronously
  // in response to a successful call to the disconnect() method of the Session object. The
  // event may also be disptached if a session connection is lost inadvertantly, as in the
  // case of a lost network connection.
  onSessionDidDisconnect (/* sessionId */) {}

  // Dispatched when a new client (including your own) has connected to the session,
  // and for every client in the session when you first connect.
  onSessionConnectionCreated (/* connectionId */) { }

  // A client, other than your own, has disconnected from the session.
  onSessionConnectionDestroyed (/* connectionId */) {}

  // A new stream, published by another client, has been created on this session.
  onSessionStreamCreated (/* streamId */) {}

  // Sent if the attempt to connect to the session fails or if the connection to the session
  // drops due to an error after a successful connection.
  onSessionStreamDidFailWithError (/* err */) {}

  // A stream from another client has stopped publishing to the session.
  onSessionStreamDestroyed (/* streamId */) {}

  /* Publisher Event Handlers */

  // The publisher has started streaming to the session.
  onPublisherStreamCreated (/* streamId */) {}

  // Sent if the publisher encounters an error. After this message is sent,
  // the publisher can be considered fully detached from a session and may be released.
  onPublisherStreamDidFailWithError (/* err */) {}

  // Sent when the publisher stops streaming.
  onPublisherStreamDestroyed (/* streamId */) {}

  /* Subscriber Event Handlers */

  // Sent when the subscriber successfully connects to the stream.
  onSubscriberDidConnect (/* streamId */) {}

  // Sent if the subscriber fails to connect to its stream.
  onSubscriberDidFailWithError (/* streamId */) {}

  // Called when the subscriber’s stream has been interrupted.
  onSubscriberDidDisconnect (/* streamId */) {}

Amazing, i'll add this to the documentation :)


Matrix Equality always false

    val gold = (0::R,0::C){(i,j) => i + j}
    val data = getMatrix(dram)
    printMatrix(data, "data")
    printMatrix(gold, "gold")
    assert(data == gold)

This assert is always thrown, even in the first IR printer

Implemented eql and neql for Matrix - Tensor5


SNAT IP used in figure does not make sense

Document URL: https://docs.pivotal.io/runtimes/pks/1-2/network-profiles-define.html
PKS Version: 1.2
Problem Section: Routable POD Networks
Problem Description: In the figure,  the exact same IP address of <IP_ADDRESS>/24 as both POD IP and the uplink interface IP of T0 is used. It would be more realistic to use a private IP for the uplink of T0 Router (for both Custom POD Networks and Routable POD Networks sections. Like an IP of "<IP_ADDRESS> /24" would make more sense since most environments has a private IP block in their datacenters. Plus 100.x.x.x block is usually consumed by T0 - T1 Router Link connections.

Thanks @dumlutimuralp! @lparis can I ask you to look at the above?

Yes, this is good feedback. I will update it. thanks
From: ben tarnoff<EMAIL_ADDRESS>Sent: Monday, December 17, 2018 2:20 PM
To: pivotal-cf/docs-pks<EMAIL_ADDRESS>Cc: Lorenzo Paris<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [pivotal-cf/docs-pks] SNAT IP used in figure does not make sense (#483)
Thanks @dumlutimuralphttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdumlutimuralp&data=02|01|lparis%40vmware.com|e6458f98bbfe4358b7e308d6646dcc21|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|636806820085198680&sdata=zBr3r3vh0G1d9iS8SncSJZedWKkqxJmusOlM6mocBaU%3D&reserved=0! @lparishttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flparis&data=02|01|lparis%40vmware.com|e6458f98bbfe4358b7e308d6646dcc21|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|636806820085198680&sdata=v0XdAN2Art0fj5yKeyXkqZLOAuwmKtS7OMgJkB4utB4%3D&reserved=0 can I ask you to look at the above?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpivotal-cf%2Fdocs-pks%2Fissues%2F483%23issuecomment-448020733&data=02|01|lparis%40vmware.com|e6458f98bbfe4358b7e308d6646dcc21|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|636806820085198680&sdata=p1YHyPzw1lqCVfGn0OAff2kOkzs502h3t5%2FXpbFPW08%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJV02WAHVU-9WMbsVQd0bEvuP95rclN6ks5u6BiUgaJpZM4ZXNNt&data=02|01|lparis%40vmware.com|e6458f98bbfe4358b7e308d6646dcc21|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|636806820085198680&sdata=8lXUoOtTt81S2UnyOvLlCIIwsrhIqtOykWqs0lpDWRo%3D&reserved=0.


PlayStation Telemetry over API

Just found these two entries when I checked my Pihole after playing on my PS

There's another entry ( takedown.api.playstation.com ) that I don't know if it should be also included.

There's another entry (takedown.api.playstation.com); I don't know if it should also be included.

Thank you for this PR David @DavidGarciaCat!
About the third domain, if we aren't sure, then let's not.
Merging!

hey @StevenBlack
I just realised the two new items were only added to the main hosts file, not the alternatives. I guess it makes sense, and then they are merged somehow, or shall I create a new update for them too?
Thanks, and sorry for the silly question

David @DavidGarciaCat the new domains are merged into the repo, and are part of the data, but won't propagate until the next release when I'll build all our lists.


[Backport] Fix accounting of bytesAdded in ReadableByteChunksFrameChannel.

Backport #12988 to 24.0.0.

This PR failed due to a recently introduced flaky web console e2e test. This is fixed here: https://github.com/apache/druid/pull/13004 I am considering this PR as passing CI


Implement new Checkout integration mode

Favor revisar para completar merge y tarjeta de Jira TD-18

Please make the review in order to merge this PR and complete TD-18 Jira

Changes have been made


Clarify "update" versus "distribute"

To make things crystal clear I suggest that the section on "distribute content" should point out that it pulls from the primary site's content library.  Similar, on "Update Distribution Point" it should use similar wording to say it pulls from the original package source location.

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

ID: 658824b0-308f-88e5-4292-52a34587a111
Version Independent ID: db08f7ce-3c4b-f7ba-e6f6-e22d00be8757
Content: Deploy content - Configuration Manager
Content Source: sccm/core/servers/deploy/configure/deploy-and-manage-content.md
Product: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @griswolm, good feedback! 😄


Update Readme

Motivation
Currently, our Readme is out of date, this PR updates the Readme and adds a Contributing guide to help developers in keeping the showcase app up to date as well as using the app as a development aid while working on the JS SDK.
Additional Information
Also included in this PR is adding package-lock.json to the .gitignore file.

@StephenCoady addressed those changes if you wouldn't mind having another look when you get a chance.

@ciaranRoche Rebase needed.

I am happy as-is. If there is a change in the branching or general versioning of the sdk or this app we can always come back and make the change later.


examples/dom-video.html - part of video and all of button hidden behind code editor

Actual Behaviour
Video and button pushed down by canvas element. Button is completely hidden and so unusable.

Button pushed down in Chrome / FireFox / Safari / Brave on Mac
Works as expected in IE on Windows 7

Expected Behaviour
"Load a video with multiple formats and toggle between playing and paused with a button press. "
Steps to reproduce it
View https://p5js.org/examples/dom-video.html in browsers other than IE.
Screenshots of the issue

Would you like to work on the issue?
Calling noCanvas(); in setup() fixes it.

I'd would be glad to make those changes in en or all the language subfolders.
If a CSS fix is preferred than someone else should handle it.

Simply adding noCanvas() should be enough for this case. You can go ahead with a PR if you like.


Block-break does not work with ensemble of plugins

Version 3.8.8-b75
I am running a Prison Server and to reduce the grind for many levels I was trying to use quests to give players money for mining blocks. However, one or more of the plugins I have prevents the block-break from occurring and I was wondering if you had any ideas.
Here is the config if you need it: https://pastebin.com/WJWiWg4p

Thanks for the report. As far as this project (and the Bukkit API) is concerned, a block is not truly broken unless it is removed from the map by a player’s hand. If a plugin has canceled the event, or is removing the block by unexpected means, then Quests has no business incrementing the objective. Consider finding which plugin is preventing the block from breaking and adjust its settings accordingly.


Add Intel Device Plugins Operator 0.19.0 to upstream-community-operators

@rojkov We are moving to github actions. Can you please rebase to latest master? Thanks

@rojkov We are moving to github actions. Can you please rebase to latest master? Thanks

Done!
Now the actions fail, but I don't quite understand why. Is it a problem of ansible or the CSV?

@rojkov, I see let me check.

@rojkov very strange. I am running it in debug mode

/retest

I rebased the PR just in case, but looks like it worsened the CI state: before the rebase at least "lemon" and "orange" were green.

@mvalarh Is it possible to reproduce the issue locally?
When I run the failing command inside a container I get
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.5 LTS (Bionic Beaver)"
...

$ ./scripts/ci/op-test lemon upstream-community-operators/intel-device-plugins-operator/0.19.0
Info: No labels defined
debug=1
Using ansible 2.5.1 ...
One can do 'tail -f /tmp/op-test/log.out' from second console to see full logs
Checking for kind binary ...
[ Preparing testing container 'op-test' from 'quay.io/operator_testing/operator-test-playbooks:latest' ]
Error: Problem pulling image 'quay.io/operator_testing/operator-test-playbooks:latest' !!!

@rojkov Sorry for dellay. I can reproduce it locally by
OP_TEST_DEBUG=1 bash <(curl -sL https://raw.githubusercontent.com/operator-framework/operator-test-playbooks/master/upstream/test/test.sh) kiwi upstream-community-operators/intel-device-plugins-operator/0.19.0 https://github.com/rojkov/community-operators intel-operator

But still not found where the problem is. Ansible or yaml itself ???

@rojkov These days i am finishing build system improvements and looking in to your issue as soon as possible.

@rojkov These days i am finishing build system improvements and looking in to your issue as soon as possible.

Thank you!

@rojkov I fixed problem with parsing, but you operator is not able to start. Can you check https://github.com/operator-framework/community-operators/pull/2750/checks?check_run_id=1591415275 ?

@mvalarh Thank you!
I looked through the logs. The relevant part seems to be that the operator's containers get stuck in the ContainerCreating phase. Unfortunately I can't find what's the culprit. Can it be dockerhub's rate limiting issue?
Is it possible to fetch more detailed logs from the pod?
TASK [deploy_olm_operator_upstream_bundle : Print operator pod log in case of an error] ***
task path: /playbooks/upstream/roles/deploy_olm_operator_upstream_bundle/tasks/main.yml:138
ok: [localhost] =>
  operator_pod_result.stdout: |-
    conditions:
    - lastProbeTime: null
      lastTransitionTime: "2020-12-21T21:36:04Z"
      status: "True"
      type: Initialized
    - lastProbeTime: null
      lastTransitionTime: "2020-12-21T21:36:04Z"
      message: 'containers with unready status: [kube-rbac-proxy manager]'
      reason: ContainersNotReady
      status: "False"
      type: Ready
    - lastProbeTime: null
      lastTransitionTime: "2020-12-21T21:36:04Z"
      message: 'containers with unready status: [kube-rbac-proxy manager]'
      reason: ContainersNotReady
      status: "False"
      type: ContainersReady
    - lastProbeTime: null
      lastTransitionTime: "2020-12-21T21:36:03Z"
      status: "True"
      type: PodScheduled
    containerStatuses:
    - image: gcr.io/kubebuilder/kube-rbac-proxy:v0.5.0
      imageID: ""
      lastState: {}
      name: kube-rbac-proxy
      ready: false
      restartCount: 0
      started: false
      state:
        waiting:
          reason: ContainerCreating
    - image: intel/intel-deviceplugin-operator:0.19.0
      imageID: ""
      lastState: {}
      name: manager
      ready: false
      restartCount: 0
      started: false
      state:
        waiting:
          reason: ContainerCreating
    hostIP: <IP_ADDRESS>
    phase: Pending
    qosClass: BestEffort
    startTime: "2020-12-21T21:36:04Z"

When testing locally with kind and OLM I stumbled upon a similar problem, but in my case it was containerd not configured to fetch images through our corporate proxy. Setting proper http_proxy env vars fixed it.

Can you try to run following command?
OP_TEST_DEBUG=1 bash <(curl -sL https://raw.githubusercontent.com/operator-framework/operator-test-playbooks/master/upstream/test/test.sh) kiwi upstream-community-operators/intel-device-plugins-operator/0.19.0 https://github.com/rojkov/community-operators intel-operator

After test fail you can check kind cluster with kubectl command. This can be done by entering testing container op-test by
docker exec -it op-test /bin/bash

@mvalarh We've reproduced the problem locally. It turned out the CI script uses a bit outdated version of OLM which is v0.16.1. This version doesn't support secret mounts for admission webhooks compatible with kubebuilder which we rely on (see https://github.com/operator-framework/operator-lifecycle-manager/issues/1315 for details). The issue was fixed in v0.17.0.
Could you please update the CI to use OLM v0.17.0? We've run the kiwi test with OLM updated to v0.17.0 and it passes.

I will bump olm version soon and i will restart test

I will bump olm version soon and i will restart test


Move Camera Capture 'Clear' button near 'Save'

ALSO:
Rethink if I should use similar interface to the capture clipboard multiple pictures 'X' for clear

Based upon the FileDropBox component
May not need to worry about this since the 'Choose' files works for all common cases.
Only place this would be needed would be if you are on a PC and want to use the camera which is not a likely scenario.


'nswag run' reports InvalidOperationException: Unsupported target framework '.NETFramework'

I am trying to generate an OpenApi document for an ASP.NET Core 2.2 WebAPI that is set for target framework=net472, as part of MSBuild.
My .csproj file has the following relevant items, gleaned from the wikis :
<TargetFramework>net472</TargetFramework>
<PackageReference Include="Microsoft.AspNetCore" Version="2.2.0" />
<PackageReference Include="NSwag.MSBuild" Version="13.1.5">...
<Target Name="NSwag" AfterTargets="Build">...
When I do a build I get the following error/info reported in the Build window:
21>NSwag command line tool for .NET Core NetCore22, toolchain v<IP_ADDRESS> (NJsonSchema v<IP_ADDRESS> (Newtonsoft.Json v<IP_ADDRESS>))
21>Visit http://NSwag.org for more information.
21>NSwag bin directory: C:\Users\peter1657\.nuget\packages\nswag.msbuild\13.1.5\tools\NetCore22
21>
21>Executing file 'nswag.json' with variables 'Configuration=Debug,OutDir=bin\Debug\net472\'...
21>System.InvalidOperationException: Unsupported target framework '.NETFramework'.
21>   at NSwag.Commands.Generation.AspNetCore.AspNetCoreToSwaggerCommand.RunAsync(CommandLineProcessor processor, IConsoleHost host) in C:\projects\nswag\src\NSwag.Commands\Commands\Generation\AspNetCore\AspNetCoreToOpenApiCommand.cs:line 89
21>   at NSwag.Commands.NSwagDocumentBase.GenerateSwaggerDocumentAsync() in C:\projects\nswag\src\NSwag.Commands\NSwagDocumentBase.cs:line 279
21>   at NSwag.Commands.NSwagDocument.ExecuteAsync() in C:\projects\nswag\src\NSwag.Commands\NSwagDocument.cs:line 81

Additionally the nswag.json looks like this (top part only):
{
  "runtime": "NetCore22",
  "documentGenerator": {
    "aspNetCoreToOpenApi": {
      "project": "MyProject.csproj",
      "msBuildProjectExtensionsPath": null,
      "configuration": "$(Configuration)",
      "runtime": null,
      "targetFramework": "net472",
      "noBuild": true,
      "verbose": true,
      "workingDirectory": null,

Any ideas what I need to adjust to make this work ?

For anyone else who ends up here who is also using .NET Framework (4.7.2) & ASP.NET Core (2.2)...
I resolved this by making two changes:
In the .csproj file I changed:
<Exec Command="$(NSwagExe_Core22) run ... " >
to
<Exec Command="$(NSwagExe) run ... " >
And in the nswag.json, I change the runtime property to "WinX64"


Custom or more Agenda views

Does this feature exist in Emacs orgmode core?
Yes
Orgmode link
https://orgmode.org/manual/Custom-Agenda-Views.html
Feature value
This would allow the user “to store and quickly access frequently used TODO and tags searches, and to create special composite agenda buffers”. My particular use case would be a “dailies” view for a GTD workflow. Show the normal agenda for the current day on a 1-day span and beneath that, all non-scheduled TODOs filtered by some tag and sorted by the priority. But I would also use this to compose weekly review views filtered by properties and sorted by, for example entry date. Ideally, this would be as flexible as in Emacs with custom commands to view saved filters and searches (can already be done with the API, i.e. require("orgmode".api.agenda).todos({ filter = "refile+TAG" }), but this approach is not built-in, flexible enough and does not work with TODOS because the query stills pops up) and the "block agenda", where several views can be combined.
Also, I would love to see a column view, but this is better tackled in another issue.
Additional context
A minimal non-working example for my usecase is
local agenda = require("orgmode").instance().agenda

local AgendaTodosView = require('orgmode.agenda.views.todos')
local AgendaView = require('orgmode.agenda.views.agenda')

local utils = require("orgmode.utils")

agenda:open_window()
agenda.win_width = utils.winwidth()
local view1 = AgendaView:new(vim.tbl_deep_extend('force', opts or {}, {
    filters = agenda.filters,
    win_width = agenda.win_width,
})):build()
local view2 = AgendaTodosView:new(vim.tbl_deep_extend('force', opts or {}, {
    filters = agenda.filters,
    win_width = agenda.win_width,
})):build()
agenda.views = { view1, view2 }
vim.b.org_agenda_type = type
return agenda:_render()

This produces the wanted agenda ("calendar") + TODOs view, but the highlighting is off, it seems the TODOs highlighting is applied to the whole buffer as if only the TODOs were present.

Sorry to bump this thread just to ask a question, but does this request imply, that it currently isn't possible to f.ex. display more than one week via the agenda shortcut / function? I'm trying to find this option, but had no luck so far

f.ex. display more than one week via the agenda shortcut

I think I don't exactly understand what you want to achieve. Could you please elaborate? Thanks :)

@nilsdev if you still around, it's possible, although the original issue is more about combining multiple agenda views which is not that easy.
There actually a simple way to save and bind commonly used match queries (oam and oaM) and agenda views overriding options. In case of match query or keyword search agenda you need to press Enter to show the agenda, it will just prefill the query for you.
So, if you like me stumbled across this issue trying to find a way to setup custom match queries in you vim config, there are a few examples of how you can do that.
A full example for match query:
local org = require('orgmode').setup({ ... })

vim.keymap.set('n', '<leader>cor', function() org.agenda:tags({ todo_only = true, search = 'recurring' }) end)

search - the desired query to match, in the example it is recurring tag
todo_only - query only TODO items

An example for agenda query function:
function() org.agenda:agenda({ org_agenda_start_day = '-3d', show_clock_report = true }) end

And a little bit more complex function would work for keywords search query (you can one line it if you like):
function()
  local AgendaSearchView = require('orgmode.agenda.views.search')
  org.agenda:open_agenda_view(AgendaSearchView, 'search', { search = 'install' })
end

To see the list of available options for different views, you can check constructors here. Refer to function *:new(opts), everything that comes from opts can be customized.

Thanks @acmilanfan for your insightful answer, I've tried tweaking it for my case but I'm a little bit lost, hope someone can guide me a bit.
I'm trying to show an agenda view of elements that match a search criteria +inbox for example. I've seen that the AgendaView doesn't have a search opts. I've tried building the filters object to match the +inbox but found no way to do this. So far I have;
local org = require('orgmode').setup({ ... })
local AgendaView = require('orgmode.agenda.views.agenda')
local AgendaFilter = require('orgmode.agenda.filter')
vim.keymap.set(
  'n',
  'gi',
  function()
    local filter = AgendaFilter:new()
    filter:parse('+inbox')
    org.agenda:open_agenda_view(
      AgendaView,
      'agenda',
      {
        org_agenda_start_day = "-0d",
        span = 3,
        filters = filter
      })
  end
)

Any idea of how to make this work?
Thanks!

@lyz-code
Thank you for your comment! There is another option for agenda, which in your case would be easier to use, it is provided in this location.
The agenda function to bind will be as simple as this:
function()
  require('orgmode.api.agenda').agenda({
    org_agenda_start_day = "-0d",
    span = 3,
    filters = '+inbox'
  })
end

Amazing, it works! thank you so much

I don't understand why but adding the local AgendaView = require('orgmode.agenda.views.agenda') line in my configuration breaks the concealment of links :S

This issue is related to https://github.com/nvim-orgmode/orgmode/issues/483