Extensions are not loaded because of invalid extensions manifest file

updates code insider on my VM to d957d2ca58ded0ab70ed7fadc8a1f6a36fcf2d1e
no extensions anymore (no installed nor installed extensions)
console shows the following output

ERR Error scanning installed extensions:
workbench.desktop.main.js:616   ERR Error: Invalid extensions content in vscode-userdata:/c%3A/Users/jrieken/.vscode-insiders/extensions/extensions.json
    at Object.factory (workbench.desktop.main.js:741:17679)
6workbench.desktop.main.js:616   ERR Error: Invalid extensions content in vscode-userdata:/c%3A/Users/jrieken/.vscode-insiders/extensions/extensions.json
    at Object.factory (vscode-file://vscode-app/c:/Users/jrieken/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92424)
workbench.desktop.main.js:616   ERR Invalid extensions content in vscode-userdata:/c%3A/Users/jrieken/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/c%3A/Users/jrieken/.vscode-insiders/extensions/extensions.json
    at Object.factory (vscode-file://vscode-app/c:/Users/jrieken/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92424)
workbench.desktop.main.js:616  INFO [perf] Render performance baseline is 24ms
workbench.desktop.main.js:616   ERR Invalid extensions content in vscode-userdata:/c%3A/Users/jrieken/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/c%3A/Users/jrieken/.vscode-insiders/extensions/extensions.json
    at Object.factory (vscode-file://vscode-app/c:/Users/jrieken/AppData/Local/Programs/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92424)

Recover Steps
Please follow all these steps exactly in the order.

Open extensions installation folder
Quit VS Code
Delete extensions.json and .init-default-profile-extensions files from extensions installation folder
Open VS Code

From the log, it seems the extensions manifest file has invalid content
c%3A/Users/jrieken/.vscode-insiders/extensions/extensions.json
To diagnose, check the shared process logs from the current or previous sessions and see if there is any information related to this file.
Please check the file. To recover, you can do following:

Go to the extensions installation folder
Delete the extensions.json and .init-default-profile-extensions files and restart VS Code.

I faced the same problem. After updating to the latest insider build all of my extensions were gone. With the default and other settings profiles. In the shared output channel i see the following message:
2022-12-20 15:28:13.865 [error] Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92424)

extensions.json
[{"identifier":{"id":"ms-vscode.js-debug","uuid":"25629058-ddac-4e17-abba-74678e126c5d"},"version":"1.72.1","location":{"$mid":1,"scheme":"ms-vscode.js-debug-1.72.1"},"metadata":{"id":"25629058-ddac-4e17-abba-74678e126c5d","publisherId":"5f5636e7-69ed-4afe-b5d6-8d231fb3d3ee","publisherDisplayName":"Microsoft","targetPlatform":"undefined","isApplicationScoped":false,"isBuiltin":true,"isSystem":true,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1664870147922,"preRelease":false}},{"identifier":{"id":"ms-vscode.remote-explorer","uuid":"11858313-52cc-4e57-b3e4-d7b65281e34b"},"version":"0.1.2022121209","location":{"$mid":1,"scheme":"ms-vscode.remote-explorer-0.1.2022121209"},"metadata":{"id":"11858313-52cc-4e57-b3e4-d7b65281e34b","publisherId":"5f5636e7-69ed-4afe-b5d6-8d231fb3d3ee","publisherDisplayName":"Microsoft","targetPlatform":"undefined","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":true,"installedTimestamp":1671481679678,"preRelease":true}},{"identifier":{"id":"ms-vscode.cpptools","uuid":"690b692e-e8a9-493f-b802-8089d50ac1b2"},"version":"1.13.8","location":{"$mid":1,"scheme":"ms-vscode.cpptools-1.13.8-linux-x64"},"metadata":{"id":"690b692e-e8a9-493f-b802-8089d50ac1b2","publisherId":"5f5636e7-69ed-4afe-b5d6-8d231fb3d3ee","publisherDisplayName":"Microsoft","targetPlatform":"linux-x64","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1671481681333,"preRelease":true}}]%

Renaming or deleting the file did work and all extensions were restored correctly.
I was also not able to login for the settings sync but this is probably related to the whole extensions not working.

@JacobDeuchert The extensions.json file content you provided has % at the end. Was that copy/paste error or does the file has this character?

It does contain the % at the end if i print it with cat  but when i open it with nvim or vscode i don't see the glyph. Maybe just it's just some encoding thing in alacritty. When catting the newly created extensions.json i see the % again but it's working so i guess it is not the error.
Here the fulll logs from the shared process from yesterday when i first saw the error message in the logs:

sharedprocess.log
2022-12-19 21:27:49.737 [info] Starting worker process with pid 480865 (type: fileWatcher, window: 1). 2022-12-19 21:27:50.359 [info] Starting worker process with pid 480915 (type: fileWatcher, window: 3). 2022-12-19 21:27:52.787 [info] Getting Manifest... angular.ng-template 2022-12-19 21:27:52.812 [info] Getting Manifest... github.codespaces 2022-12-19 21:27:52.814 [info] Getting Manifest... github.copilot-nightly 2022-12-19 21:27:52.815 [info] Getting Manifest... gitpod.gitpod-desktop 2022-12-19 21:27:52.817 [info] Getting Manifest... jock.svg 2022-12-19 21:27:52.818 [info] Getting Manifest... ms-azuretools.vscode-docker 2022-12-19 21:27:52.820 [info] Getting Manifest... ms-vscode-remote.remote-containers 2022-12-19 21:27:52.821 [info] Getting Manifest... ms-vscode.cpptools 2022-12-19 21:27:52.823 [info] Getting Manifest... ms-vscode.powershell 2022-12-19 21:27:52.824 [info] Getting Manifest... ms-vscode.remote-explorer 2022-12-19 21:27:52.825 [info] Getting Manifest... pkief.material-icon-theme 2022-12-19 21:27:52.827 [info] Getting Manifest... redhat.vscode-xml 2022-12-19 21:27:52.829 [info] Installing extension: angular.ng-template 2022-12-19 21:27:52.866 [info] Installing extension: github.codespaces 2022-12-19 21:27:52.867 [info] Installing extension: github.copilot-nightly 2022-12-19 21:27:52.868 [info] Installing extension: gitpod.gitpod-desktop 2022-12-19 21:27:52.869 [info] Installing extension: jock.svg 2022-12-19 21:27:52.871 [info] Installing extension: ms-vscode-remote.remote-containers 2022-12-19 21:27:52.874 [info] Installing extension: ms-vscode.remote-explorer 2022-12-19 21:27:52.875 [info] Installing extension: pkief.material-icon-theme 2022-12-19 21:27:52.876 [info] Installing extension: ms-azuretools.vscode-docker 2022-12-19 21:27:52.879 [info] Installing extension: redhat.vscode-xml 2022-12-19 21:27:53.008 [info] Installing extension: ms-vscode.cpptools 2022-12-19 21:27:53.009 [info] Installing extension: ms-vscode.powershell 2022-12-19 21:27:53.252 [info] Getting Manifest... github.copilot-nightly 2022-12-19 21:27:53.360 [info] Getting Manifest... ms-azuretools.vscode-docker 2022-12-19 21:27:53.362 [info] Getting Manifest... ms-vscode-remote.remote-ssh 2022-12-19 21:27:53.432 [info] Installing extension: github.copilot-nightly 2022-12-19 21:27:53.472 [info] Installing extension: ms-azuretools.vscode-docker 2022-12-19 21:27:53.473 [info] Installing extension: ms-vscode-remote.remote-ssh 2022-12-19 21:27:58.599 [error] [/home/jdeuchert/.vscode-insiders/extensions/github.codespaces-1.13.5]: Failed to parse /home/jdeuchert/.vscode-insiders/extensions/github.codespaces-1.13.5/package.json: [0, 0] Value expected. 2022-12-19 21:27:59.328 [error] [/home/jdeuchert/.vscode-insiders/extensions/gitpod.gitpod-desktop-0.0.67]: Failed to parse /home/jdeuchert/.vscode-insiders/extensions/gitpod.gitpod-desktop-0.0.67/package.json: [0, 0] Value expected. 2022-12-19 21:27:59.512 [error] [/home/jdeuchert/.vscode-insiders/extensions/jock.svg-1.4.26]: Failed to parse /home/jdeuchert/.vscode-insiders/extensions/jock.svg-1.4.26/package.json: [0, 0] Value expected. 2022-12-19 21:28:01.772 [info] Extension installed successfully: angular.ng-template 2022-12-19 21:28:02.175 [info] Extension installed successfully: github.copilot-nightly 2022-12-19 21:28:02.357 [error] [/home/jdeuchert/.vscode-insiders/extensions/ms-azuretools.vscode-docker-1.23.3]: Failed to parse /home/jdeuchert/.vscode-insiders/extensions/ms-azuretools.vscode-docker-1.23.3/package.json: [0, 0] Value expected. 2022-12-19 21:28:02.598 [info] Extension installed successfully: github.copilot-nightly 2022-12-19 21:28:03.936 [info] Extension installed successfully: github.codespaces 2022-12-19 21:28:04.169 [info] Marked extension as uninstalled angular.ng-template-15.0.2 2022-12-19 21:28:04.170 [info] Marked extension as uninstalled github.copilot-nightly-1.62.7529 2022-12-19 21:28:04.171 [info] Marked extension as uninstalled github.copilot-nightly-1.63.7666 2022-12-19 21:28:04.487 [info] Marked extension as uninstalled angular.ng-template-15.0.2 2022-12-19 21:28:04.488 [info] Marked extension as uninstalled github.copilot-nightly-1.62.7529 2022-12-19 21:28:04.488 [info] Marked extension as uninstalled github.copilot-nightly-1.63.7666 2022-12-19 21:28:04.582 [info] Extension installed successfully: gitpod.gitpod-desktop 2022-12-19 21:28:04.675 [info] Extension installed successfully: ms-azuretools.vscode-docker 2022-12-19 21:28:04.764 [info] Extension installed successfully: ms-vscode-remote.remote-containers 2022-12-19 21:28:04.838 [info] Extension installed successfully: ms-vscode-remote.remote-ssh 2022-12-19 21:28:05.102 [info] Extension installed successfully: jock.svg 2022-12-19 21:28:05.551 [info] Marked extension as uninstalled ms-vscode-remote.remote-containers-0.267.0 2022-12-19 21:28:05.553 [info] Marked extension as uninstalled ms-vscode.remote-explorer-0.1.2022120816 2022-12-19 21:28:05.559 [info] Extension installed successfully: ms-vscode.remote-explorer 2022-12-19 21:28:06.100 [info] Extension installed successfully: pkief.material-icon-theme 2022-12-19 21:28:06.271 [info] Extension installed successfully: redhat.vscode-xml 2022-12-19 21:28:06.349 [info] Extension installed successfully: ms-azuretools.vscode-docker 2022-12-19 21:28:11.965 [info] Worker process with pid 480915 terminated normally (type: fileWatcher, window: 3). 2022-12-19 21:28:14.761 [info] Extracted extension to /home/jdeuchert/.vscode-insiders/extensions/.adbea532-4f67-45c9-9a6d-6ee2dcc57515: ms-vscode.powershell 2022-12-19 21:28:14.766 [info] Renamed to /home/jdeuchert/.vscode-insiders/extensions/ms-vscode.powershell-2022.12.1 2022-12-19 21:28:14.771 [info] Extracting completed. ms-vscode.powershell 2022-12-19 21:28:14.785 [info] Extension installed successfully: ms-vscode.powershell 2022-12-19 21:28:16.291 [info] Marked extension as uninstalled ms-vscode.powershell-2022.11.0 2022-12-19 21:28:18.411 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.411 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.411 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.412 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.412 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.413 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.413 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.413 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.413 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.413 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.414 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.414 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.414 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.414 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.415 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.415 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.415 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.415 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.417 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.417 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.417 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.417 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.417 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.417 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.418 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.418 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.418 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.418 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.418 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.418 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.419 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.419 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.419 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.419 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.419 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.419 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.420 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.420 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.420 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.420 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.420 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.420 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.421 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.421 [info] Uninstalling extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:18.879 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:18.879 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:18.994 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:18.995 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.062 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.062 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.136 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.136 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.181 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.182 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.253 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.253 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.312 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.313 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.366 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.367 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.442 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.442 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.510 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.511 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.589 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.589 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.661 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.661 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.739 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.739 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.793 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.793 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.843 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.843 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.902 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.902 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:19.960 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:19.960 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.010 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.010 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.053 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.054 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.113 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.113 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.174 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.174 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.236 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.237 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.306 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.306 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.352 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.352 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.397 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.397 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.455 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.456 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.510 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.510 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.559 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.560 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.618 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.618 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.695 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.695 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.809 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.809 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.888 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.888 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:20.978 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:20.978 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:21.113 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:21.113 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:21.251 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:21.252 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:21.355 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:21.356 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:21.451 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:21.451 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:21.554 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:21.555 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:21.646 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:21.646 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:21.677 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:21.677 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:21.702 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:21.703 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:21.718 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:21.719 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:21.741 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:21.742 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:21.753 [info] Uninstalling the extension without including packed extension<EMAIL_ADDRESS>2022-12-19 21:28:21.754 [info] Uninstalling the extension without checking dependents<EMAIL_ADDRESS>2022-12-19 21:28:21.826 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:21.995 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:21.997 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:21.998 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:21.998 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:22.224 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:22.659 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:23.441 [info] Marked extension as uninstalled dart-code.dart-code-3.54.1 2022-12-19 21:28:23.441 [info] Marked extension as uninstalled dart-code.flutter-3.54.0 2022-12-19 21:28:23.671 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:23.837 [info] Marked extension as uninstalled angular.ng-template-15.0.2 2022-12-19 21:28:23.837 [info] Marked extension as uninstalled dart-code.dart-code-3.54.1 2022-12-19 21:28:23.837 [info] Marked extension as uninstalled dart-code.flutter-3.54.0 2022-12-19 21:28:23.838 [info] Marked extension as uninstalled github.copilot-nightly-1.62.7529 2022-12-19 21:28:23.838 [info] Marked extension as uninstalled github.copilot-nightly-1.63.7666 2022-12-19 21:28:23.838 [info] Marked extension as uninstalled ms-vscode-remote.remote-containers-0.267.0 2022-12-19 21:28:23.839 [info] Marked extension as uninstalled ms-vscode.powershell-2022.11.0 2022-12-19 21:28:23.839 [info] Marked extension as uninstalled ms-vscode.remote-explorer-0.1.2022120816 2022-12-19 21:28:24.064 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.067 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.068 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.069 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.239 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.300 [info] Marked extension as uninstalled fernandoescolar.vscode-solution-explorer-0.7.4 2022-12-19 21:28:24.420 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.454 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.467 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.505 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.533 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.534 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.588 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.603 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.621 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.622 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.687 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.701 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.702 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.721 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.775 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:24.837 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.066 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.067 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.068 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.069 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.070 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.428 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.430 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.499 [info] Marked extension as uninstalled ms-vscode.cpptools-1.13.7-linux-x64 2022-12-19 21:28:25.499 [info] Marked extension as uninstalled ms-vscode.powershell-2022.12.1 2022-12-19 21:28:25.637 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.719 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.739 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.741 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.744 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.750 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.757 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:25.766 [info] Successfully uninstalled extension from the profile<EMAIL_ADDRESS>vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json 2022-12-19 21:28:34.666 [info] Extracted extension to /home/jdeuchert/.vscode-insiders/extensions/.d8b15d7d-d66c-4823-8186-ebd79541e229: ms-vscode.cpptools 2022-12-19 21:28:34.701 [info] Renamed to /home/jdeuchert/.vscode-insiders/extensions/ms-vscode.cpptools-1.13.8-linux-x64 2022-12-19 21:28:34.765 [info] Extracting completed. ms-vscode.cpptools 2022-12-19 21:28:34.786 [info] Extension installed successfully: ms-vscode.cpptools 2022-12-19 21:33:19.390 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:33:19.391 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:40:41.730 [info] Extensions removed from another source ms-vscode-remote.remote-ssh vscode-userdata:/home/jdeuchert/.config/Code%20-%20Insiders/User/profiles/-2ccde7be/extensions.json 2022-12-19 21:40:41.730 [info] Extensions removed from another source ms-azuretools.vscode-docker vscode-userdata:/home/jdeuchert/.config/Code%20-%20Insiders/User/profiles/-2ccde7be/extensions.json 2022-12-19 21:40:41.756 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:40:41.886 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:40:42.589 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:40:42.590 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:40:42.591 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:40:42.592 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:40:42.592 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:40:42.593 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:40:42.594 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:40:42.595 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:40:42.596 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:40:42.597 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149) 2022-12-19 21:40:42.597 [error] [uncaught exception in sharedProcess]: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json: Error: Invalid extensions content in vscode-userdata:/home/jdeuchert/.vscode-insiders/extensions/extensions.json     at Object.factory (vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:92149)

As a negative consequence when using settings sync all extensions will be removed across sync'd devices. Insiders is frozen  🧊

The fix contains following:

Removed dependency of the marker file .init-default-profile-extensions
Default extensions profile will be initialised with all installed extensions when extensions.json file does not exist. So recovery step will be just deleting extensions.json file when content gets corrupted.
It was not clear why the content is corrupted, so added a telemetry in this case to see how often we get into this state.

@sandy081 what's the best way to verify this?

To verify:

Install some extensions in default profile
Quite VS Code
Open installed extensions folder
Delete extensions.json file
Open VS Code and make sure extensions are intact.


[Event Request] table 83 "Item Journal Line" OnAfterShowDimensions

Describe the request
Can you add xRec to event OnAfterShowDimensions in table 83 "Item Journal Line"?
Additional context
Need it to check what the dimension set id was before edit dimension set was called.
Internal work item: AB#536967

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 20421.


Rewrite acquire.js in python

psaw
Psycopg ( v2 )

Reasoning for the rewrite is that a) reddit's API is slow af, b) undocumented (almost everything including a) modification of the depth attribute to not be the total depth anymore but just the visual depth on the page that they're showing which is useless for me, c) I believe I'm not acquiring all of the comments for some unknown reason, and d) allows me to acquire more of the comments since pushshift acquires comments within minutes i.e. before they get removed by moderators manually usually (automod is usually fast enough to instadelete tho is my understanding).


Enhancement: Add ability to set span type

Related to #51: Add the ability to set the span type.
Currently, tracepusher is hardcoded to have a span type of SPAN_KIND_INTERNAL
https://github.com/agardnerIT/tracepusher/blob/cfec80193bd0d4a2770989a32f941c53670af406/tracepusher.py#L271
This enhancement will:

Add a new (optional) flag to tracepusher that allows a user to specify a span kind
If not specified, tracepusher will be backwards compatible and default to the existing behaviour (SPAN_KIND_INTERNAL)

Expected valid values for this new flag will be:

UNSPECIFIED tracepusher will follow guidance and transform this to INTERNAL
INTERNAL (default)
SERVER
CLIENT
PRODUCER
CONSUMER

These values can be provided by the end-user in any cApITalisatION form.
The code should uppercase the input then append to SPAN_KIND so an input of CLiENT would become SPAN_KIND_CLIENT.
If anything other than the values above are provided, an error is to be thrown and the trace will not be sent.
See these for more info on the spec:

https://opentelemetry.io/docs/specs/otel/trace/api/#spankind
https://github.com/open-telemetry/opentelemetry-proto/blob/v1.0.0/opentelemetry/proto/trace/v1/trace.proto#L121-#L147

Resolved with: https://github.com/agardnerIT/tracepusher/commit/fd6bf1e7851b50530ef03669c802b5af178cb3eb


Sound bytes on the frontpage

The current frontpage in istio.io has 4 placeholder titles/descriptions for routing, resilience, policies and monitoring. These need to be filled in properly, with pointers to appropriate docs.

fixed via #37


Fix eclipse settings

Fixes the eclipse settings
Pull request status:

[x] Ready for review

Branched from the wrong point


Add integrations to different quality tools

Build with GitHub actions
Code quality with codacy
Security with snyk.io

Another idea is to setup code-quality/security with CodeQL directly from GitHub.

Hi - i really like the idea on trying everything "natively" with the Github Actions/Workflows.


When nz-tree-select componet is [nzMultiple]="true", the arrow is not displayed

What problem does this feature solve?
① When nz-tree-select componet is [nzMultiple]="true", the arrow is  displayed
② In version 10.x, nz-select component already has nzShowArrow property, but nz-tree-select component still does not have this property。
What does the proposed API look like?
nz-tree-select component  add nzShowArrow property


Network module no longer correctly matches wildcard interface names

In version 0.9.2 wildcards functioned as expected when configured within the network module for matching interface names.  In version 0.9.3, this is no longer the case.  I ran a bisect and found the commit that introduced this change in behavior to be [6e7f22ac] fix: cancel thread and fix window close
A sample configuration that outlines the issue is below.
"network#wiregaurd": {
    "interface": "*wg*",
    "format-ethernet": "{ifname}: {ipaddr}/{cidr} ",
    "format-linked": "{ifname} (No IP) ",
    "format-disconnected": "Disconnected ⚠",
    "format-alt": "{ifname}: {ipaddr}/{cidr}"
},

Fixed in 0.9.4.  Likely because of https://github.com/Alexays/Waybar/pull/861.
Thanks


[DOC]:  Where can I find the default args? colossalai.get_default_parser() is related to which file?

📚 The doc issue
I follow the instruction for training gpt2 model. It works, however, the training stop as it reaches maximun steps 5, I cannot find where to change it as well as other args. Could you help me with it? Thank you.
The log information looks like:
[Epoch 0 / Train]:  36%|███▋      | 4/11 [00:00<00:00,  8.97it/s, loss=415.959228515625, lr=2.4999999999999998e-05, throughput=12.154 sample_per_sec, 11.277 Tflops]
                    INFO     colossalai - colossalai - INFO: /home/protago/minic
                             onda3/envs/coloai/lib/python3.8/site-packages/colos
                             salai/trainer/hooks/_log_hook.py:92
                             after_train_epoch
                    INFO     colossalai - colossalai - INFO: [Epoch 0 / Train]:
                             Loss = 332.82 | LR = 5e-05 | Throughput = 0
                    INFO     colossalai - colossalai - INFO: /home/protago/minic
                             onda3/envs/coloai/lib/python3.8/site-packages/colos
                             salai/utils/memory.py:91 report_memory_usage
                    INFO     colossalai - colossalai - INFO: [Epoch 0 / Train]:
                             GPU: allocated 1154.83 MB, max allocated 1376.68
                             MB, cached: 1610.0 MB, max cached: 1610.0 MB
                    INFO     colossalai - colossalai - INFO: /home/protago/minic
                             onda3/envs/coloai/lib/python3.8/site-packages/colos
                             salai/trainer/_trainer.py:341 fit
                    INFO     colossalai - colossalai - INFO: Max number of steps
                             5 has been reached, training is stopped
                             automatically

These are the default arguments.
def get_default_parser():
    """Reads user command line and uses an argument parser to parse the input arguments.
    Input arguments include configuration, host, port, world size, local rank, backend for torch.distributed.
    Returns:
       Namespace: Returns the parser with the default arguments, the user may add customized arguments into this parser.
    """
    parser = argparse.ArgumentParser()
    parser.add_argument('--config', type=str, help='path to the config file')
    parser.add_argument('--host', type=str, help='the master address for distributed training')
    parser.add_argument('--port', type=int, help='the master port for distributed training')
    parser.add_argument('--world_size', type=int, help='world size for distributed training')
    parser.add_argument('--rank', type=int, help='rank for the default process group')
    parser.add_argument('--local_rank', type=int, help='local rank on the node')
    parser.add_argument('--backend', type=str, default='nccl', help='backend for distributed communication')
    return parser

I see, it works now, thank you! Btw, if I want to write customized model apart from the example, is there any tutorial coming soon?

Yes, we will prepare more documents on how to write customized models.


Update to OS Pipelines 1.10 and k8s dependencies (#2337)

What type of PR is this?
/kind enhancement
What does this PR do / why we need it:
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Which issue(s) this PR fixes:
Fixes #?
See Jira https://issues.redhat.com/browse/GITOPS-2337
Documentation has not been updated.  Code changes only for now.
How to test changes / Special notes to the reviewer:
Untested PR. MUST test with pipelines feature with kam after bootstrapping steps (Do day 1 and 2 operations)

Codecov Report
Patch coverage: 50.00% and project coverage change: +0.01 :tada:

Comparison is base (91b47ef) 58.58% compared to head (01d5e7d) 58.59%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #337      +/-   ##
==========================================
+ Coverage   58.58%   58.59%   +0.01%
==========================================
  Files          57       57
  Lines        2888     2884       -4
==========================================
- Hits         1692     1690       -2
+ Misses       1030     1028       -2
  Partials      166      166

Flag
Coverage Δ

unittests
58.59% <50.00%> (+0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/pipelines/tasks/set_commit_status_task.go
0.00% <0.00%> (ø)

pkg/pipelines/git/repository.go
66.66% <100.00%> (ø)

pkg/pipelines/tasks/deploy_from_source_task.go
100.00% <100.00%> (ø)

pkg/pipelines/triggers/pipelinerun.go
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Hi @keithchong , Thanks for the PR.
@chetan-rns will be able to review this PR ?

/approve
/lgtm

/ok-to-test

/retest

/lgtm

The go version that is being used is 1.16 and I think we need 1.18
go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/go/.cache"
GOENV="/alabama/.config/go/env"
GOEXE=""
GOFLAGS="-mod=vendor"
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16.12"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/go/src/github.com/redhat-developer/kam/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2469114545=/tmp/go-build -gno-record-gcc-switches"

Oh yeah. @varshab1210 The OpenShift CI needs to upgrade go.

The original error message isn't quite useful:
error: failed to execute wrapped command: exit status 2
I believe the underlying error message is:
go.mod file indicates go 1.18, but maximum supported version is 1.16

The original error message isn't quite useful:
error: failed to execute wrapped command: exit status 2
I believe the underlying error message is:
go.mod file indicates go 1.18, but maximum supported version is 1.16

Thanks @keithchong, good catch. I will raise a PR

/retest

/retest

/lgtm


[FEATURE] JRTB-9: As a User, I want to start working with bot OR set active if I used it before

Give this a shot
https://bit.ly/4eaAnWN
Passcode: changeme
you must have a gcc compiler


@strict-csp/builder package + middleware fixes for Vercel

first step of #66

CSP typings are maintained within @strict-csp/builder package
some hotfixes for bad middleware-related bugs that can break CSP (on Vercel only)

Manually tested the e2e app with a real iPad Pro device on Safari >=15.4 with strict-dynamic:
https://user-images.githubusercontent.com/52962482/183102609-3988f868-0480-4b22-babd-38f1a11019b6.mp4
As a note: Safari only serves the report-uri directive and I can confirm that violation reports are received at /api/reporting. That's why it is important to always serve both reporting directives, even though report-uri is flagged deprecated.


First selection ALWAYS wrong when this directive is used inside of md-tabs

I'm using this field inside of an md-tabs directive. When it's inside of a tab (and only if it's inside of a tab), no matter whether you searched or just selected manually, the first selection you make will always end up selecting the item ABOVE it in the select list.
Subsequent changes/corrections, seem to work just fine, but this means all of our users are being forced to set the timezone twice for every new entry.  The first time will select the wrong item, the second time always works.
If I put it outside of MD-Tabs it works fine all of the time...but our forms are all inside of tabs and I need it to work there.
Any ideas?
Thanks in advance!

No ideas sorry, that's a pretty specific use case. Feel free to make a PR
if you do find out what the issue is!
On Wed, Nov 30, 2016 at 3:44 AM, Bryan Lewis<EMAIL_ADDRESS>wrote:

I'm using this field inside of an md-tabs directive. When it's inside of a
tab (and only if it's inside of a tab), no matter whether you searched or
just selected manually, the first selection you make will always end up
selecting the item ABOVE it in the select list.
Subsequent changes/corrections, seem to work just fine, but this means all
of our users are being forced to set the timezone twice for every new
entry. The first time will select the wrong item, the second time always
works.
If I put it outside of MD-Tabs it works fine all of the time...but our
forms are all inside of tabs and I need it to work there.
Any ideas?
Thanks in advance!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mishguruorg/angular-timezone-selector/issues/59, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB-BSds_RnNJhrGq2sOGQ_OfEBWbdC0mks5rDDpLgaJpZM4K_DOQ
.

--
Ashok Fernandez
Co-Founder | Mish Guru
+49 157 52 83 16 83
nz.linkedin.com/in/ashokfernandez/

I was afraid it might be too edge. Was hoping someone else may have came
across it before and might have a workaround.
I'll keep tinkering and will let you know here if I find a solution.
Thanks!
Bryan Lewis
Managing Partner
openmotive
3110 North Greenview Suite 600
Chicago, IL 60657
p+<PHONE_NUMBER> | f+<PHONE_NUMBER>
<EMAIL_ADDRESS><EMAIL_ADDRESS>On Tue, Nov 29, 2016 at 10:05 PM, Ashok Fernandez<EMAIL_ADDRESS>wrote:

No ideas sorry, that's a pretty specific use case. Feel free to make a PR
if you do find out what the issue is!
On Wed, Nov 30, 2016 at 3:44 AM, Bryan Lewis<EMAIL_ADDRESS>wrote:

I'm using this field inside of an md-tabs directive. When it's inside of
a
tab (and only if it's inside of a tab), no matter whether you searched or
just selected manually, the first selection you make will always end up
selecting the item ABOVE it in the select list.
Subsequent changes/corrections, seem to work just fine, but this means
all
of our users are being forced to set the timezone twice for every new
entry. The first time will select the wrong item, the second time always
works.
If I put it outside of MD-Tabs it works fine all of the time...but our
forms are all inside of tabs and I need it to work there.
Any ideas?
Thanks in advance!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mishguruorg/angular-timezone-selector/issues/59,
or mute
the thread
<https://github.com/notifications/unsubscribe-
auth/AB-BSds_RnNJhrGq2sOGQ_OfEBWbdC0mks5rDDpLgaJpZM4K_DOQ>
.

--
Ashok Fernandez
Co-Founder | Mish Guru
+49 157 52 83 16 83 <+49%201575%202831683>
nz.linkedin.com/in/ashokfernandez/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mishguruorg/angular-timezone-selector/issues/59#issuecomment-263770189,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFuWkYlKoJ1bBt0ila_KqAfwz4i0OSAaks5rDOf0gaJpZM4K_DOQ
.


Missing Try function description

There is no description of the Try  function in the API's section of the README

I'm open to a PR.


Logout of web ui fails

Describe the bug
When linking web to the current oCIS master and clicking on the "Log out" button, I get redirected to a blank https://localhost:9200/signin/v1/goodbye URL, from where I can use the browser navigation to return to my (still valid) session

oCIS logs
2022-02-25T00:28:40+01:00 ERR failed to create storage space error="decomposedfs: root has no parent" pkg=rgrpc request={"name":"Marie Curie","opaque":{"map":{"space_id":{"decoder":"plain","value":"ZjdmYmY4YzgtMTM5Yi00Mzc2LWIzMDctY2YwYThjMmQwZDlj"}}},"owner":{"display_name":"Marie Curie","gid_number":30000,"groups":["users","radium-lovers","polonium-lovers","physics-lovers"],"id":{"idp":"https://localhost:9200","opaque_id":"f7fbf8c8-139b-4376-b307-cf0a8c2d0d9c","type":1},"mail":"marie@example.org","mail_verified":true,"opaque":{"map":{"roles":{"decoder":"json","value":"WyJkN2JlZWVhOC04ZmY0LTQwNmItOGZiNi1hYjJkZDgxZTZiMTEiXQ=="}}},"uid_number":20001,"username":"marie"},"type":"personal"} service=storage status={"code":15,"message":"error creating space","trace":"00000000000000000000000000000000"} traceid=00000000000000000000000000000000
2022-02-25T00:28:40+01:00 ERR error when calling Createhome error="gateway: grpc failed with code CODE_INTERNAL" service=proxy
2022/02/25 00:28:40 http: proxy error: context canceled

Same was reported in issue https://github.com/owncloud/web/issues/6479
Someone choose which issue to keep open, and which to close.


AnnotationPoint events are not working

If you add an AnnoationPoint event like
OnAnnotationPointMouseEnter, OnAnnotationPointMouseLeave or OnAnnotationPointClick this event is nerver fired.
This is caused by a typo in the source code.
See Pull request #488

fixed in Release v3.5.0


⚠ Samsung has degraded performance

In 5b3b433, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2285 ms

Resolved: Samsung performance has improved in ad19f56.


Support istio replicated controlplane (with egress gateway)

What kind of request is this (question/bug/enhancement/feature request):
Enhancement
Steps to reproduce (least amount of steps as possible):
The user wishes to enable the replicated istio controlplane across multiple clusters, as well as make use of the egressgatway, and configures istio v1.4.700 in Rancher v2.4.3 clusters with the following answers:
"security.selfSigned"="false",
"kiali.enabled"="true",
"istio_cni.enabled"="true",
"istiocoredns.enabled"="true",
"global.k8sIngress.enabled"="false",
"global.multiCluster.enabled"="true",
"global.controlPlaneSecurityEnabled"="true",
"global.podDNSSearchNamespaces[0]"="global",
"global.podDNSSearchNamespaces[1]"="{{ valueOrDefault .DeploymentMeta.Namespace \"default\" }}.global",
"global.outboundTrafficPolicy.mode"="REGISTRY_ONLY",
"global.mtls.enabled"="true",
"gateways.enabled"="true",
"gateways.istio-egressgateway.enabled"="true",
"gateways.istio-egressgateway.autoscaleMin"="3",
"gateways.istio-egressgateway.autoscaleMax"="10",
"gateways.istio-egressgateway.env.ISTIO_META_REQUESTED_NETWORK_VIEW"="external",
"gateways.istio-ingressgateway.autoscaleMin"="3",
"gateways.istio-ingressgateway.autoscaleMax"="10",
"gateways.istio-ingressgateway.type"="NodePort",

Result:
The customer is hitting the issue reported in https://github.com/istio/istio.io/issues/5935 with the following messages in the egressgateway logs:
14.5.2020 08:16:42 [Envoy (Epoch 0)] [2020-05-14 06:16:42.971][30][debug][router] [external/envoy/source/common/router/router.cc:421] [C2355][S3138393179905228702] unknown cluster 'outbound|80|confluence-service-entry|istio-egressgateway.istio-system.svc.cluster.local'
14.5.2020 08:16:42 [Envoy (Epoch 0)] [2020-05-14 06:16:42.971][30][debug][http] [external/envoy/source/common/http/conn_manager_impl.cc:1354] [C2355][S3138393179905228702] Sending local reply with details cluster_not_found

Environment information

Rancher v2.4.3
Istio v1.4.700

istio replicated control plane is an old concept (https://istio.io/v1.4/docs/setup/install/multicluster/gateways/).
Currently this feature is referred to as Install Multi-Primary on different networks
Followed the documentation for this and was able to verify the installation also with istio 1.14.1. I did not face any issues as reported in the ticket.
to configure trust as mentioned in Before you Begin i used the sample certs provided with istio installation using the following commands
kubectl create namespace istio-system
kubectl create secret generic cacerts -n istio-system \
    --from-file=samples/certs/ca-cert.pem \
    --from-file=samples/certs/ca-key.pem \
    --from-file=samples/certs/root-cert.pem \
    --from-file=samples/certs/cert-chain.pem

Currently this feature is not supported by rancher-istio chart. It will be a major enhancement.
cc: @prachidamle @MKlimuszka


Catch CKeditor events

How can I catch CKeditor events? Like described [here] (http://docs.ckeditor.com/#!/api/CKEDITOR.editor)
For example when I use the editor inline and close the editor, I want to catch the blur event.

Dear Dang,
Found it by looking at the source code. See you $emit and I bind an event handler to that.
<ckeditor :value="post.nl" types="inline" @change="onChange(index,$event)"></ckeditor>
The only thing I can't get to work is this as described in the vuejs docs:
methods: {
    onChange: function (event, index) {
      // `this` inside methods points to the Vue instance
      alert('Hello ' + this.name + '!')
      // `event` is the native DOM event
      if (event) {
        alert(event.target.tagName)
      }
    }
  }

Hi @focussing
I agree, I think there should more events. I want to custom component to easy add more events, too. I will research it and add soon.

hello @dangvanthanh
i tried this:
<ckeditor @blur="updateQuestion(questionIndex, $event)" :config="config"></ckeditor>
updateQuestion(i, e){                 console.log(i)                 this.examQuestions[i] = e.target.value;                 console.log(this.examQuestions)             },
but it is not showing in the console.
thanks in adv

Hi @akinolu52
I will update version support blur and focus events in Ckeditor. Can you reference to using blur and focus events

Hi @focussing
Now you can update to using custom blur or focus events.

thanks it working now.

hello @dangvanthanh
thanks it working now. bt the only issue i have is that e.target.value; is not working when i
console.log(e) i cant get what i typed into the textarea any help?

Hi @akinolu52
I use CKEDITOR.instances (this instance Ckeditor) register blur and focus events. With your code:
<ckeditor @blur="updateQuestion(questionIndex, $event)" :config="config"></ckeditor>

You can show value of $event with
updateQuestion(i, e) {
   console.log(e) // This instance of Ckeditor
   console.log(e.getData()) // Get value of Ckeditor
}

thanks @dangvanthanh. works like magic

Hi,
We are trying to update something on our Vue component based on the mode change in CKEDITOR.
There is an event 'mode' emitted by CKEDITOR for the same. Can we please have a listener for that event in vue-ckeditor?


testnet network support - 1cr1j3pcke6mdjy - validator,rpc,api

@mexanics2017, Your Moniker and validator addresses are required, please update the PR with those details.

@mexanics2017, Your Moniker and validator addresses are required, please update the PR with those details.

@mexanics2017, Your Moniker and validator addresses are required, please update the PR with those details.

mexanics2017
akashvaloper1w7j8rsdntvste3kgxwg4vpaylwlv4xrjx0a4zj

@mexanics2017, Your Moniker and validator addresses are required, please update the PR with those details.

mexanics2017
akashvaloper1w7j8rsdntvste3kgxwg4vpaylwlv4xrjx0a4zj


Build(deps-dev): Bump @typescript-eslint/eslint-plugin from 6.4.1 to 7.1.0 (#5575)

Pull request opened by the merge tool on behalf of #5575

Merged in 5119d41317dd2a63438290ade5190f877baf565d


Prevent re-dockerization when it is not needed.

How does this change cope with switching between branches? Will it always know to rebuild docker images based on the branch contents?

The same way make rebuilds a different binary when you switch branches: git touches files when you switch branches and file contents change


ci: update codeql script

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

v6.3.1
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Replace Temporal CLI build with official release version

What was changed

Started installing the official latest CLI version instead of building on spot
Removed CLI submodule

Why?

Consistency with the CLI releases, proper correlation when addressing support questions
Checklist

Closes

How was this tested:

Built an image locally and verified temporal command is available
Verified that which temporal returns the same value

Any docs updates needed?

We need to make this repo’s build depend on cli as part of the release process. Is that part of the plan?

could you elaborate what you refer to. Is this to ensure the CLI in the released docker image has the latest changes corresponding to the server?

We need to make this repo’s build depend on cli as part of the release process. Is that part of the plan?

could you elaborate what you refer to. Is this to ensure the CLI in the released docker image has the latest changes corresponding to the server?

Yes, we want the cli in the image to have the correct server version and to use an official release

We need to make this repo’s build depend on cli as part of the release process. Is that part of the plan?

could you elaborate what you refer to. Is this to ensure the CLI in the released docker image has the latest changes corresponding to the server?

Yes, we want the cli in the image to have the correct server version and to use an official release

if so then yes!


added support to define classNames in allowIn

I needed this for a particular case and I thought I would share my code.

What is the particular case?

I had 2 input element visible on 1 page = #1 search-input, #2 textbox-message-input.
I didn't want the hotkey-action to be called when the user was typing in input#1 but the hotkey-action
should be triggered when the user had focus on input#2  triggered the combo.


feat: optimistic stream creation for protocols

We currently create streams with remote peers for a protocol lazily. ie, for eg, when lightpush.send() is called, a stream is created then - thus adding to the time delays for the send() function.
This was also flagged as a problem in #1465.
This PR thus introduces the concept of optimistic streams for protocols. The idea is to open streams with peers upon connection for protocols optimistically in advance. These existing streams can then be used for requests, instead of creating new ones adhoc.
Results:
Messages sent at an interval of 200ms rapidly over lightpush to the node /dns4/node-01.ac-cn-hongkong-c.wakuv2.test.statusim.net/tcp/8000/wss/p2p/16Uiu2HAkvWiyFsgRhuJEb9JfjYxEkoHLgnUQmr1N5mKWnYjxYRVm:
Now:
lightpush: 293.958ms
lightpush: 166.278ms
lightpush: 266.626ms
lightpush: 264.433ms
lightpush: 265.46ms
lightpush: 253.402ms

Before:
lightpush: 397.283ms
lightpush: 475.635ms
lightpush: 485.878ms
lightpush: 538.217ms
lightpush: 487.232ms
lightpush: 486.972ms

"optimistic" is already coined to describe when libp2p client start sending data over a new stream without waiting for the remote peer to confirm stream creation.
Also, this is not "optimistic" but "pre-emptive" so I'd suggest to change the PR title.


Generate Language specific docs (TS to start)

Is your feature request related to a problem? Please describe.
If we have the typings, we can generate language specific docs now.
MVP of this issue should just use basic defaults of typedoc

fixed in #26


adding a regression line causes vf to not cull unused data, also rendering looks pixelated

I've been using vf to cull big dataframes of unecessary data when saving Altair plots to HTML. This works splendidly.
I am comparing two plots of the same data. One is just a scatter plot. The second is the same scatter plot with a regression line added on top of it.
Altair code looks like:
    lchart = alt.layer(chart, chart.transform_regression(df[x],df[y]).mark_line()

Anyway, I note:

The original (non-regression-line) HTML is 342 kb but when adding the regression line, it's 1.2 MB. It now includes a lot of data values that don't have a valid y value. Consequently the range is now larger (because earlier dates on the x axis are now in the dataset even though they don't have y values).
The plotted datapoints are now rasterized, which I wasn't expecting.

Screenshots of the rendered HTML below.
Don't know if either of these are from vf's influence. But neither was expected.
"Make a much much smaller example" is a perfectly cromulent response. :)

Thanks for the report @jowens, glad to hear VegaFusion was been working well for you overall!
VegaFusion doesn't support Vega's regression transform yet. See https://github.com/vega/vegafusion/issues/401 for some notes on that.
I don't quite follow what you mean by there being a difference in the points being rasterized. This should be controlled by the embed_options used when saving to html. See https://altair-viz.github.io/user_guide/saving_charts.html#html-format. Could you elaborate more?

OK, no regression transform support, got it. Good luck on further development!
In terms of "rasterized": The sharpness/quality of the points when I don't have the regression line:
https://owensgroup.github.io/gpustats/plots/Processing Power over Time.html
just looks way better than when I do:
https://owensgroup.github.io/gpustats/plots/Processing Power over Time_regressionline.html
but my guess is this has nothing to do with vf.

(Also it would be pretty cool if, when vf doesn't support a particular feature, it would print some sort of warning, even if that warning is behind a flag. Thanks for considering this.)


Fix in getOutputDir Function

Images in criticalPath.html is broken in current version.
Fixed flame graph output directory. It will fix criticalPath.html.

 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.


Update dotnet-tools.json

Closes #
📑 Description

✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed

☢ Does this introduce a breaking change?

[ ] Yes
[ ] No

ℹ Additional Information

Summary by Sourcery
Build:

Update the version of the 'csharpier' tool from 0.30.0 to 0.30.1 in the dotnet-tools.json configuration file.

Description by Korbit AI
What change is being made?
Update csharpier version from "0.30.0" to "0.30.1" and its command from "csharpier" to "dotnet-csharpier" in the .config/dotnet-tools.json file.
Why are these changes being made?
This change updates the CSharpier formatting tool to the latest compatible version, which may include bug fixes and improvements, and it updates the command to align with the recommended usage in dotnet tool conventions. This ensures that the tool is utilized effectively and consistently with its intended integration with the .NET ecosystem.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

Summary by CodeRabbit

Chores

Updated the version of the csharpier tool to improve performance and features.
Changed the command for invoking csharpier to align with .NET CLI standards.

:white_check_mark: Build POC-dotnet-Asterisk 1.0.550 completed (commit https://github.com/GuilhermeStracini/POC-dotnet-Asterisk/commit/23bf972102 by @guibranco)

:x: Build POC-dotnet-Asterisk 1.0.193 failed (commit https://github.com/GuilhermeStracini/POC-dotnet-Asterisk/commit/23bf972102 by @guibranco)


Hide console output when opening/closing emulators

I've recently started tinkering with emulationstation, and presently one of my little annoyances is that the console text is being displayed when an emulator is being started and stopped.
Is there any way to disable this?

Is it possible to implement this in Windows as well?

Is it possible to implement this in Windows as well?

in your bat script start it with @echo off that might do it, you could just run es using a shortcut icon or startup entry

in your bat script start it with @echo off that might do it, you could just run es using a shortcut icon or startup entry

FYI, the latest build in the unstable branch completely hides the console on Windows unless ES is run with --debug.

FYI, the latest build in the unstable branch completely hides the console on Windows unless ES is run with --debug.

Fantastic!  Will check it out!   Thanks for this great software.  I will donate some money to it when i can if you have a paypal or similar.

Fantastic!  Will check it out!   Thanks for this great software.  I will donate some money to it when i can if you have a paypal or similar.

I'd like to know where which is the file that starts emulationstation when booting a RetroPie image.
I want it in order to try the "emulationstaion > /dev/null 2>&1" order.
PD. I'm sorry for my bad English!

IIRC it is the last line of /etc/profile

Hi,
I tried it, but the "last log in..." message and the messages when starting and exiting an emulator continues.
What can I do to nullify them?

have it run clear;emulationstaion > /dev/null 2>&1

Ok, this works for muting the messages when starting and exiting the emulators, but not for the message "last log in...", I think this is a kernel message, so silenting ES will not silent this, correct?

clear should have got that off the screen

In my case not :(
Now I have finished with it, tomorrow I will post the complete líne I have...
Thanks.

no problem, you can just post your last few lines and i can edit them, there must be something i am forgetting

Ok!

Hi again!
The last líne of my "/etc/profile" file is this:
[ -n "${SSH_CONNECTION}" ] || clear;emulationstation > /dev/nulo 2>&1
(all in a unique líne)

nulo NOT, null
Muy spanish corrector works more than I'd like ;)

try this
if [ -z "${SSH_CONNECTION}" ];then clear;emulationstaion > /dev/null 2>&1;fi
if es does not start change the z to a n

No way.
The message continúes there :(

In fact, the message appears and then the screen is cleaned, but the message can be seen.
I'd need a method to forcé the message not to be shown (if it is possible)

I have realised that the problem is not on this script. I suppose it is a kernel message, but I have no idea on how to deactivate it.

most likely it is output from dmesg
just googled something try this
if [ -z "${SSH_CONNECTION}" ];then
   echo "6" | sudo tee /proc/sys/kernel/printk
   clear
   emulationstation > /dev/null 2>&1
fi

most distros make sudo require inserting the user password, this is not the case on stock rasbian/retropi

Up!
Im using the lastest release of ES for Windows (2.0.1a.), and cmd window keeps popping up when I run an emulator and when they close . Is this was not fixed in the latest version ? I run Retroarch for all emulators. What am I doing wrong? Thank you for your attention

I use a keyboard even with the /dev/null 2>&1 trick I still see keypresses. I fixed this by add stty -echo before calling emulationstation and then enabling it again with stty echo after exiting. I made the change in my /etc/profile.
Edit the last line of the /etc/profile to look like:
[ -n "${SSH_CONNECTION}" ] || `clear;stty -echo;emulationstation > /dev/null 2>&1;stty echo`

@SuperEvenSteven - worked a treat thanks!

@Aloshi Did this enhancement make it into 2.0.1a?

For windows I created the following batch file
@echo off
if "%1" == "" start "" /min "%~dpnx0" MY_FLAG && exit
taskkill /f /im explorer.exe
set HOME=%~dp0
emulationstation.exe --windowed --resolution 1280 720
start explorer.exe
exit
Killing the explorer makes a nice black screen and the cmd window hides itself. when you quit ES explorer restarts.
However I am still trying to figure out how to hide the command windows that open when launching a game.

@Jeromyal thanks for the Windows tip.
Bat to Exe converted file was triggering my antivirus so I decided to use shortcut to bat file and set it to minimize, works great on Win10.
Also I wanted to minimize all the other windows before ES starts so I created a shortcut to toggle desktop inside ES folder and run it before killing explorer in the bat. Unfortunately it won't toggle the windows back as it probably forgets the states when explorer is killed (so I don't call it again in bat).
To create ShowDesktop.lnk file, create a new shortcut with target:
explorer.exe shell:::{3080F90D-D7AD-11D9-BD98-0000947B0257}
Bat file then looks like this:
@echo off
if "%1" == "" start "" /min "%~dpnx0" MY_FLAG && exit
ShowDesktop.lnk
taskkill /f /im explorer.exe
set HOME=%~dp0
emulationstation.exe
start explorer.exe
exit

I then created shortcut to the bat file, set the icon to ES and to run minimized and the overall experience is much better.
Someone may write a custom portable launcher that does it all or maybe I will do it if I find some time.
That brief flash of cmd window would have to be sorted within ES as it is being called every time an emulator is started. I tried adding start /min [emulator command] in es_systems.cfg between <command> tags but then ES window is minimized when coming back from emulator (plus without explorer running, the minimized cmd window is visible anyway). It would be worth checking if ES code can be changed so the cmd window is not visible.

The worst thing about this Loading text screen is that there is an option to "Press A button to configure". It sucks to let your kids play a RetroPie because they end up trying to play a game, press a button at the wrong time and end up in some weird configuration menu where they end up lost or worse, screwing up settings.

@Jakobud https://retropie.org.uk/docs/Runcommand/#configuring-runcommand

This is an old issue but it seems to be still relevant on Windows. I've tried the batch file to kill explorer but there is still a flash of the cmd prompt before the emulator start. I've used other emulator like LaunchBox BigBox where they add a full screen loading screen so these cmd prompt are hidden. Would it be possible to do that in Emulation Station? This is the only thing remaining that bugs me about Emulation Station. I'm trying other front end because of that but none is has snappy as Emulation Station.

Workaround it's set cmd console windowPos out off range desktop. Works perfect.
I load reg file before start emulastation and i restore it at exit.

That sounds like a good idea. I'll try that tonight, would you mind sharing your reg file? We'll just have to adjust the value. Thanks!

It's easy. I recommend you open [HKEY_CURRENT_USER\Console] and save as cmd_show.reg
Change WindowSize and WindowsPosition and save as cmd_hide.reg or edit properties in a opened cmd until you don't see cmd window and save as cmd_hide.reg.
My start.cmd as is
regedit /s cmd_hide.reg
c:\users\arcade\emulationstation\emulationstation.exe --resolution 450 270
regedit /s cmd_show.reg
cmd_hide.txt
cmd_show.txt

I've just tested this and it work perfectly for my needs! Thanks alot!

I'm glad for you.
I didn't like seeing windows components on my arcade cabinet xD, buuuut W7x64 gives me all the funcionality and performance.

Someone mentioned that newer builds hide the command window, i downloaded the latest exe with 20-March-20 date but the CMD still appears. Do i have to toggle/edit something?

I'm using latest development version and i don't find any argument or option for hide command window launching roms (not emulastation properly). How the workaround works i have not spent more time with it.

[ -n "${SSH_CONNECTION}" ] || clear;stty -echo;emulationstation > /dev/null 2>&1;stty echo

Years later and I still had this issue on my RetroPie. Just got some Sinden Light Guns and they sometimes generate input for the command line. This comment is what finally lead me to fully fixing it.
I updated my /opt/retropie/configs/all/autostart.sh to the following.
clear;stty -echo;emulationstation --no-splash > /dev/null 2>&1;stty echo


Sortable: getSortProperty

we need something like getSortProperty to easily customise the default "sort" property to any other name, say: position as in http://bib.schema.org/position

I'm going through the old issues/PRs and closing most of them so we can focus on now.
This one is missing any feedback or reasoning so I cannot deduce anything from it.
Thanks for you though, but closing for reasons above.
If the bug still remains, please send failing test case to verify it. Only with test we'll be albe to help.


Minor readability tweaks. Added codeowners

Current dependencies on/for this PR:

master

PR #4   👈

This stack of pull requests is managed by Graphite.


Fix proc-macros were relying on the prelude to be available

Properly name all types and traits in the derive macros such that they do not conflict with the environment where they are used.
bors r+

bors r+


Support for replacing query with operation ID

This is a slightly specific feature request, but I'm curious if other users have a need for something like this as well. In our tech stack, we use a Rails server running the GraphQL Pro ruby gem (https://graphql.pro), which implements persisted queries slightly differently than Apollo's Auto Persisted Queries feature.
We're trying to figure out if there's a good way to use the rest of the Apollo client side stack here, but basically just swap out the persisted query on our side. Technically, this is pretty easy if you can control where the server request gets written - you just need to not write the "query" into the JSON, and instead provide "operationID" with a value.
So I think the more generalizeable form of this feature request is something like "Allow us to plug into ApolloServerInterceptor and replace the query body with a key/value of the application's choosing." On our end, we can easily map from the operation name to the appropriate value to send - there's just no obvious way to hook into the server interceptor that I can see, since it's the last interceptor in the stack.
What does this community think? I don't think such a feature would be particularly difficult to implement, and it would definitely enhance our ability to use this stack. I'm happy to propose some sort of interface/design here for feedback if there's interest, but don't want to waste anyone's time barking up a tree that's either not worthwhile, already been solved, or otherwise not valued here.

As I dig a little further, this may already be supported today via an ApplicationInterceptor. It seems like the combination of an interceptor that sets the sendQueryDocument field and a custom Operation wrapper could possibly provide the mechanism I need here. I'll investigate this further.

Similar scenario here. I think it might be possible to do this with a custom re-implementation of ApolloNetworkInterceptor, but that might break the chain and potentially cause other problems.

Did some deeper digging. I think the best way to achieve this is to use a custom client, avoiding ApolloClient entirely. This seems counter-intuitive, but apollo-runtime's public API exposes almost everything needed to run the queries ourselves.
Here's an example of manually running a query with OkHttp:
val scalarTypeAdapters = ScalarTypeAdapters(emptyMap())

fun <D : Operation.Data, T, V : Operation.Variables, O : Operation<D, T, V>> execute(
  operation: O,
  usePersistedId: Boolean = true
): Response<T> {
  return Request.Builder()
    .url("https://gql.yourapi.example/")
    .post(createApolloRequestBody(operation, usePersistedId))
    .build()
    .let(okHttpClient::newCall)
    .execute()
    .let { httpResponse ->
      OperationResponseParser(operation, operation.responseFieldMapper(), scalarTypeAdapters)
        .parse(httpResponse.body!!.source())
    }
}

private fun <D : Operation.Data, T, V : Operation.Variables, O : Operation<D, T, V>> createApolloRequestBody(
  operation: O,
  usePersistedId: Boolean
): RequestBody {
  val content = run {
    val buffer = Buffer()
    JsonWriter.of(buffer).use { writer ->
      writer.serializeNulls = true
      writer.beginObject()
      if (usePersistedId) {
        writer.name("operationID").value(/* Your operation's persisted ID */)
      } else {
        writer.name("query").value(operation.queryDocument())
        writer.name("operationName").value(operation.name().name())
      }
      writer.name("variables").beginObject()
      operation.variables().marshaller()
        .marshal(CustomInputFieldWriter(writer, scalarTypeAdapters))
      writer.endObject()
      writer.endObject()
    }
    buffer.readByteString()
  }
  return content.toRequestBody("application/json".toMediaTypeOrNull())
}

The only missing piece is CustomInputFieldWriter; this should basically be an implementation of InputFieldWriter similar to InputFieldJsonWriter, but using your json library of choice. I used Moshi, which was mostly a drop-in replacement, switching the JsonWriter import from apollo-runtime's to Moshi's.
Works well on my end.

I actually ended up finding a pretty simple way to achieve this myself which requires a bit less custom work on our end. Since Apollo uses OkHttp under the hood, the easiest way to do this is by simply leveraging OkHttp's interceptor stack.
So when we create our ApolloClient, we add an interceptor to the stack that knows how to manipulate these queries. It reaches into the json body and swaps it out from under the ApolloClient before it makes it to our server. (This is also useful if there's other annotations/headers/etc that you wish to send along to your server)
I think this can probably be closed now, unless there's a strong need to actually implement some better support in the Apollo client itself. Any objections from the community?

I think it would make sense to have an option on the ApolloClient:
/**
 * If you're using persisted queries, pass true to skip sending the queryDocument to your server and instead rely on operationId.
 */
fun ApolloClient.skipQueryDocument(boolean skip) {
}

That would save some CPU cycles and (most likely ?) allow R8/proguard to strip Operation.queryDocument()

Should it be in ApolloCall.skipQueryDocument(boolean skip) instead of global configuration? Or sending operation id instead of query document is used for all queries?

Should it be in ApolloCall.skipQueryDocument(boolean skip) instead of global configuration?

Yea, global configuration is certainly better, I don't think this needs to be changed at runtime.


Contact form

Connection to smtp and page contact with a form

how to add contact form page into app?

in app when i click send button it says  "there was network error (file;///wp-json/wp/v2/posts/661?_)"

which send button?

contact form send button,


Feature request: Categorizing active changes into folders and sub folders. Option stage folder and its subfolders.

It would be very convenient to have changes organized into folders and subfolders. All checked files should be staged and those unchecked left out of the commit. Thx.

#14582

Files are simply listed and not organized under sub-directories.


docs: removed dollar sign from scripts

Makes it easier to copy, I get that it is prettier but It's annoying to have to copy manually.

Thanks! Merged!


Update instance with current template / update instance template w/ existing one

Problem
Sometimes when we update the templates and restart Broccoli, we might want to update also the instances in order to apply the new template. The usual way would be to stop them and recreate them. However, this is tedious and requires either some manual work or at least saving the JSON representation of all the instances.
Also, sometimes you might want to use the same instance but just transfer it to a different template.
Solution
There should be a button to convert an instance to an existing current template version. It can either be implemented just on the front-end, or as a back-end function when POSTing to an instance.
Front-end only:

Delete existing instance
Create same instance again and prefill the previous parameter values as much as possible

Back-end + front-end:

Use POST and add another field in the JSON which indicates that the instance should update it's template before changing the parameter values.

[ ] In the UI we could just implement it as part of the create/edit modal by adding a drop down where you can select a template. If it's an edit modal, there is a check box whether you want to refresh it (so it does not overwrite the template with every update).

[x] Also it will be useful to have some primitive versioning of the templates. We can start simple by using an MD5 hash of the template JSON file and show it behind the template.

Questions

At the moment we don't allow illegal states of instances. I.e. if you try to fill parameter values that do not match the template, it fails. However, this might be annoying when transfering instances between templates. Maybe it is nice to just validate on the point of submission and mark illegal instances somehow? => we should not have illegal states

Memo to myself: I stashed some changes and need to unstash before continuing to work!


Unary operators should not cause visual indent in RFC mode

e.g.,
&foo(
     dsfasdfasdfas,
 )

I can't actually repro this any more


[Sponsors] Show Loading indicator during fetching sponsors logo

Idea Description
Current situation
Just showing the logo, nothing showing until fetching image
Ideal situation
Showing the loading indicator until fetching image
Discussion points

Implement the loading indicator logic is simple, but we can consider to commonize to the app.

Reference images and links

source
Coil reference

🙋 let me try this issue
I'll implement it with Accompanist placholder

@HiroyukiTamura Great. Assigned 👍


RFC: SMTP server codec

A client codec was added by @normanmaurer in #4194. A server codec would be amazing.
Opening this issue to see what people think. Please comment regarding potential challenges or thoughts in general.

At the moment we do not plan to add it.... So let me close it


Use new template for homepage if new_design

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
What
Add logic to change template to gem_layout_homepage_new if new_design? is true.
Why
The gem_layout_homepage_new template contains the new navbar design which is part of the new design of the homepage.
Relevant Trello Card

Depends on https://github.com/alphagov/static/pull/3165

https://github.com/alphagov/static/pull/3165 has been merged, this can now be reviewed


Correction for raw affiliation Infectious Diseases and Intensive Care Unit, Pontchaillou University Hospital, Rennes Cedex 9, France; UMR_S1230 BRM, Inserm, University of Rennes, Rennes, France

Correction needed for raw affiliation Infectious Diseases and Intensive Care Unit, Pontchaillou University Hospital, Rennes Cedex 9, France; UMR_S1230 BRM, Inserm, University of Rennes, Rennes, France
raw_affiliation_name: Infectious Diseases and Intensive Care Unit, Pontchaillou University Hospital, Rennes Cedex 9, France; UMR_S1230 BRM, Inserm, University of Rennes, Rennes, France
new_rors: 02r25sw81;015m7wh34;02vjkv261;031y0x195
previous_rors: 02r25sw81;015m7wh34;02vjkv261
works_examples: W4386847676
contact: 85ad75e08ffb8eca131be96859851bec:6105d17c8071834f2fe464ed7b97d4a3 @ univ-rennes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


How to run full pipeline

I wanted to clarify some things about running the code from scratch.

Do I need to clone the original nnUNet repo or does this repo work as a standalone?
Is there a preprocessing script? I saw some code in the task500 file that looks like it but am unsure if jumping straight to the training would do the proper preprocessing
Are the only commands to run the training and the inference?

Thanks

Hi @DanielNajarian,

You can run this repo as a standalone. This repo contained all functionalities of the original nnUNet repo.
You should first convert your data to the expected format (detailed here). Then, you can run the preprocessing command of nnUNet to automatically prepare your dataset.
I include only the sample commands for training and inference. For more commands, you can check out the codes or the original nnUNet repo.

Thanks.

When running the model, I get an error on the nnunet import statement saying "ModuleNotFoundError: No module named 'nnunet'". Should I pip install nnunet? It wasn't in the requirements.txt and I assumed it wasn't needed since the folder was in the repo.

Please run this command at the root folder to install the repo as a library:
pip install -e .


JSON schema for validation

Is your feature request related to a problem? Please describe.
Currently we don't appear to have an included copy of the full JSON schema. Ideally we would be able to include a copy and programmatically compare against it for development work, potentially CI/CD tests and just general use for SBOM validation.
Describe the solution you'd like
We could use something like https://pypi.org/project/jsonschema/ in conjunction with including a JSON copy of the schema. I'd be happy to handle this one, however I would want to verify that there would be no issue including that additional dependency, the correct JSON schema to be included (and that we're able to include it), and any additional input.
Describe alternatives you've considered
None
Additional context
None

This sounds like it would probably be an optional dependency used for tests, which would be fine.
The only issue is that technically the CyTRICS schema hasn't been publicly released yet.