VS Code extensions suddenly won't load or update/install

Does this issue occur when all extensions are disabled?: N/A

VS Code Version: 1.75.0
OS Version: Windows 10 version 22H2 build 19045.2486

Everything has been working fine for several years.  I used VS Code Thursday (2/2) as usual with no issues.  I was OOO Friday but first thing Monday (2/6) I opened VS Code and got several errors from extensions.  I tried to update the Python extension since that's the language that I was using but it also failed.  So, I tried uninstalling the extension, which worked, but then when trying to install it again it fails.  So, I decided to start over.  See below.
Steps to Reproduce:

Renamed the C:\Users\bqd4.vscode directory so a new one would be created
Renamed the %APPDATA%\Code directory so a new one would be created
Uninstalled VS Code
Restarted my workstation
Installed latest version of VS Code (1.75.0)
Started VS Code; Output window contains:

2023-02-07 07:40:53.336 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'github.vscode-pull-request-github' wants API proposal 'commentsResolvedState' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2023-02-07 07:40:53.788 [info] Started initializing default profile extensions in extensions installation folder. file:///c%3A/Users/bqd4/.vscode/extensions
2023-02-07 07:40:54.024 [info] Completed initializing default profile extensions in extensions installation folder. file:///c%3A/Users/bqd4/.vscode/extensions
2023-02-07 07:40:56.960 [info] [perf] Render performance baseline is 48ms

Tried to install the Python extension v2023.2.0
Returns: Error while installing 'Python' extension. Please check the [log](command:workbench.action.showWindowLog) for more details.

The Output (log) contains:
2023-02-07 07:51:02.703 [error] Error: UnhandledException,UnhandledException,UnhandledException
    at vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89578
    at Array.reduce (<anonymous>)
    at E (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89564)
    at ne.D (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:80916)
    at async ne.z (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:78417)
    at async ne.installFromGallery (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:74855)
2023-02-07 07:51:02.804 [error] UnhandledException,UnhandledException,UnhandledException: Error: UnhandledException,UnhandledException,UnhandledException
    at vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89578
    at Array.reduce (<anonymous>)
    at E (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89564)
    at ne.D (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:80916)
    at async ne.z (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:78417)
    at async ne.installFromGallery (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:74855)

Installing from a vsix file has this result:
Returns UnhandledException,UnhandledException
The Output contains:
2023-02-07 08:09:40.102 [error] UnhandledException,UnhandledException: Error: UnhandledException,UnhandledException
    at vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89578
    at Array.reduce (<anonymous>)
    at E (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89564)
    at ne.D (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:80916)
    at async ne.z (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:78417)
    at async ne.install (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:90:158273)

Tried to install Docker extension v1.23.3
Returns Error while installing 'Docker' extension. Please check the [log](command:workbench.action.showWindowLog) for more details.

The Output (log) contains:
2023-02-07 07:59:12.131 [error] Signature: UnhandledException
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:62:17985)
    at async $.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:90:171351)
2023-02-07 07:59:12.203 [error] UnhandledException: Signature: UnhandledException
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:62:17985)
    at async $.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:90:171351)

Tried to install the Eclipse Keymap extension v0.16.1 (this is the only extension that installs successfully)
Tried to install the Extension Pack for Java v0.25.7
Returns Error while installing 'Extension Pack for Java' extension. Please check the [log](command:workbench.action.showWindowLog) for more details.

The Output (log) contains:
2023-02-07 08:04:23.373 [error] Error: UnhandledException,UnhandledException,UnhandledException,UnhandledException,UnhandledException
    at vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89578
    at Array.reduce (<anonymous>)
    at E (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89564)
    at ne.D (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:80916)
    at async ne.z (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:78417)
    at async ne.installFromGallery (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:74855)
2023-02-07 08:04:23.418 [error] UnhandledException,UnhandledException,UnhandledException,UnhandledException,UnhandledException: Error: UnhandledException,UnhandledException,UnhandledException,UnhandledException,UnhandledException
    at vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89578
    at Array.reduce (<anonymous>)
    at E (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89564)
    at ne.D (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:80916)
    at async ne.z (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:78417)
    at async ne.installFromGallery (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:74855)

At this point I'm out of ideas.  What do I need to do to make it work again?

The last build that will let me load extension is 1.73.1

Can you please share following log while you reproduce the issue?

F1 > Open View... > Shared

Can you also please share the content in following file?

F1 > Open Extensions Folder > extensions.json

@huhqwerty The output log you shared is the window log. I am asking for another log - F1 > Open View... > Shared

I reverted to 1.73.1 as @simonamc mentioned and everything works again.

@huhqwerty Glad that old version is working for you, but we would like to understand why the latest version is not working. Can you please provide us this log?
F1 > Open View... > Shared
I am suspecting that the errors you are seeing are related to extension signing verification.
2023-02-07 07:59:12.131 [error] Signature: UnhandledException
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:62:17985)
    at async $.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:90:171351)
2023-02-07 07:59:12.203 [error] UnhandledException: Signature: UnhandledException

I would like to confirm that from the requested above log.

Have you got a chance to update to our latest 1.75.1 build?
If it still does not work in 1.75.1, can you please try adding following setting in your user settings file?

"extensions.verifySignature": false

@sandy081 after installing 1.75.1 that worked for me and curiously it continued to work after I rolled back to 1.75.0 when it didn't before. I've been running VS code from WSL I don't know if that is a confounding factor. Normally this works great for me, being able to run linux in windows is a game changer

@sandy081 Uninstalled 1.73.1 and reinstalled 1.75.0.  This is with all but the python extension pre-installed.  Below is the Output when I tried to install the python extension:
2023-02-10 07:20:26.823 [info] Marked extension as uninstalled dbaeumer.vscode-eslint-2.4.0
2023-02-10 07:20:26.824 [info] Marked extension as uninstalled ms-python.isort-2022.8.0
2023-02-10 07:20:26.824 [info] Marked extension as uninstalled ms-python.python-2022.18.2
2023-02-10 07:20:26.825 [info] Marked extension as uninstalled ms-python.vscode-pylance-2023.1.10
2023-02-10 07:20:26.825 [info] Marked extension as uninstalled ms-toolsai.jupyter-2022.9.1303220346
2023-02-10 07:20:26.825 [info] Marked extension as uninstalled ms-toolsai.jupyter-keymap-1.0.0
2023-02-10 07:20:26.826 [info] Marked extension as uninstalled ms-toolsai.jupyter-renderers-1.0.14
2023-02-10 07:20:26.827 [info] Marked extension as uninstalled ms-toolsai.vscode-jupyter-cell-tags-0.1.6
2023-02-10 07:20:26.828 [info] Marked extension as uninstalled ms-toolsai.vscode-jupyter-slideshow-0.1.5
2023-02-10 07:20:26.880 [info] Deleted from disk dbaeumer.vscode-eslint c:\Users\bqd4\.vscode\extensions\dbaeumer.vscode-eslint-2.2.6
2023-02-10 07:20:27.563 [info] Starting worker process with pid 20948 (type: fileWatcher, window: 1).
2023-02-10 07:20:29.456 [info] WSL is not installed, so could not detect WSL profiles
2023-02-10 07:21:14.087 [info] Getting Manifest... ms-python.python
2023-02-10 07:21:14.094 [info] Installing extension: ms-python.python
2023-02-10 07:21:15.313 [info] Getting Manifest... ms-toolsai.jupyter
2023-02-10 07:21:15.728 [info] Getting Manifest... ms-toolsai.jupyter-keymap
2023-02-10 07:21:15.822 [info] Getting Manifest... ms-toolsai.jupyter-renderers
2023-02-10 07:21:15.908 [info] Getting Manifest... ms-toolsai.vscode-jupyter-cell-tags
2023-02-10 07:21:16.002 [info] Getting Manifest... ms-toolsai.vscode-jupyter-slideshow
2023-02-10 07:21:16.085 [info] Getting Manifest... ms-python.vscode-pylance
2023-02-10 07:21:16.164 [info] Getting Manifest... ms-python.isort
2023-02-10 07:21:16.432 [info] Installing extension: ms-toolsai.jupyter ms-python.python
2023-02-10 07:21:16.433 [info] Installing extension: ms-toolsai.jupyter-keymap ms-python.python
2023-02-10 07:21:16.433 [info] Installing extension: ms-toolsai.jupyter-renderers ms-python.python
2023-02-10 07:21:16.433 [info] Installing extension: ms-toolsai.vscode-jupyter-cell-tags ms-python.python
2023-02-10 07:21:16.433 [info] Installing extension: ms-toolsai.vscode-jupyter-slideshow ms-python.python
2023-02-10 07:21:16.434 [info] Installing extension: ms-python.vscode-pylance ms-python.python
2023-02-10 07:21:16.434 [info] Installing extension: ms-python.isort ms-python.python
2023-02-10 07:21:17.517 [info] Removed the extension from uninstalled list: ms-toolsai.jupyter-keymap
2023-02-10 07:21:17.572 [info] Removed the extension from uninstalled list: ms-toolsai.vscode-jupyter-cell-tags
2023-02-10 07:21:17.579 [info] Removed the extension from uninstalled list: ms-toolsai.vscode-jupyter-slideshow
2023-02-10 07:21:19.073 [error] RequestService#request (browser) - error https://ms-toolsai.gallery.vsassets.io/_apis/public/gallery/publisher/ms-toolsai/extension/jupyter/2023.1.2010391206/assetbyname/Microsoft.VisualStudio.Services.VSIXPackage?redirect=true&install=true {}
2023-02-10 07:21:20.009 [error] Error while installing the extension: ms-toolsai.jupyter-renderers
2023-02-10 07:21:20.011 [error] [uncaught exception in sharedProcess]: UnhandledException: Signature: UnhandledException
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:62:17985)
    at async $.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:90:171351)
2023-02-10 07:21:20.011 [error] [uncaught exception in sharedProcess]: UnhandledException: Signature: UnhandledException
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:62:17985)
    at async $.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:90:171351)
2023-02-10 07:21:20.023 [error] Error while installing the extension: ms-python.python
2023-02-10 07:21:20.023 [error] [uncaught exception in sharedProcess]: UnhandledException: Signature: UnhandledException
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:62:17985)
    at async $.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:90:171351)
2023-02-10 07:21:20.024 [error] [uncaught exception in sharedProcess]: UnhandledException: Signature: UnhandledException
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:62:17985)
    at async $.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:90:171351)
2023-02-10 07:21:20.913 [error] Error while installing the extension: ms-toolsai.jupyter
2023-02-10 07:21:20.914 [error] [uncaught exception in sharedProcess]: UnhandledException: Signature: UnhandledException
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:62:17985)
    at async $.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:90:171351)
2023-02-10 07:21:20.914 [error] [uncaught exception in sharedProcess]: UnhandledException: Signature: UnhandledException
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:62:17985)
    at async $.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:90:171351)
2023-02-10 07:21:21.056 [info] Rollback: Uninstalled extension ms-toolsai.jupyter-keymap
2023-02-10 07:21:21.056 [info] Rollback: Uninstalled extension ms-toolsai.vscode-jupyter-cell-tags
2023-02-10 07:21:21.057 [info] Rollback: Uninstalled extension ms-toolsai.vscode-jupyter-slideshow
2023-02-10 07:21:21.057 [error] Failed to install extension. ms-python.python
2023-02-10 07:21:21.057 [error] Error: UnhandledException,UnhandledException,UnhandledException
    at vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89578
    at Array.reduce (<anonymous>)
    at E (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89564)
    at ne.D (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:80916)
    at async ne.z (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:78417)
    at async ne.installFromGallery (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:74855)
2023-02-10 07:21:21.085 [info] Marked extension as uninstalled ms-toolsai.jupyter-keymap-1.0.0
2023-02-10 07:21:21.085 [info] Marked extension as uninstalled ms-toolsai.vscode-jupyter-cell-tags-0.1.6
2023-02-10 07:21:21.086 [info] Marked extension as uninstalled ms-toolsai.vscode-jupyter-slideshow-0.1.5
2023-02-10 07:21:21.144 [info] Marked extension as uninstalled dbaeumer.vscode-eslint-2.4.0
2023-02-10 07:21:21.144 [info] Marked extension as uninstalled ms-python.isort-2022.8.0
2023-02-10 07:21:21.145 [info] Marked extension as uninstalled ms-python.python-2022.18.2
2023-02-10 07:21:21.145 [info] Marked extension as uninstalled ms-python.vscode-pylance-2023.1.10
2023-02-10 07:21:21.146 [info] Marked extension as uninstalled ms-toolsai.jupyter-2022.9.1303220346
2023-02-10 07:21:21.147 [info] Marked extension as uninstalled ms-toolsai.jupyter-keymap-1.0.0
2023-02-10 07:21:21.147 [info] Marked extension as uninstalled ms-toolsai.jupyter-renderers-1.0.14
2023-02-10 07:21:21.147 [info] Marked extension as uninstalled ms-toolsai.vscode-jupyter-cell-tags-0.1.6
2023-02-10 07:21:21.147 [info] Marked extension as uninstalled ms-toolsai.vscode-jupyter-slideshow-0.1.5

Here is the corresponding extensions.json:
[{"identifier":{"id":"alphabotsec.vscode-eclipse-keybindings","uuid":"0c9d43ad-d1d0-4e2a-8246-fe7b296162a8"},"version":"0.16.1","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/alphabotsec.vscode-eclipse-keybindings-0.16.1","scheme":"file"},"relativeLocation":"alphabotsec.vscode-eclipse-keybindings-0.16.1","metadata":{"id":"0c9d43ad-d1d0-4e2a-8246-fe7b296162a8","publisherId":"a9e49c66-52a1-4cb2-a5e7-7b109ab15be6","publisherDisplayName":"Alphabot Security","targetPlatform":"undefined","updated":true,"isPreReleaseVersion":false,"preRelease":false,"installedTimestamp":1653353346877}},{"identifier":{"id":"dbaeumer.vscode-eslint","uuid":"583b2b34-2c1e-4634-8c0b-0b82e283ea3a"},"version":"2.2.6","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/dbaeumer.vscode-eslint-2.2.6","scheme":"file"},"relativeLocation":"dbaeumer.vscode-eslint-2.2.6","metadata":{"id":"583b2b34-2c1e-4634-8c0b-0b82e283ea3a","publisherId":"29859a75-d81b-4f0e-8578-2c80ecee6f99","publisherDisplayName":"Microsoft","targetPlatform":"undefined","updated":true,"isPreReleaseVersion":false,"preRelease":false,"installedTimestamp":1657022872959}},{"identifier":{"id":"dotjoshjohnson.xml","uuid":"0cb81da2-1880-4755-9995-0ae9cc728e20"},"version":"2.5.1","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/dotjoshjohnson.xml-2.5.1","scheme":"file"},"relativeLocation":"dotjoshjohnson.xml-2.5.1","metadata":{"id":"0cb81da2-1880-4755-9995-0ae9cc728e20","publisherId":"0a72d6f9-f644-4e7d-93fe-34389b97e913","publisherDisplayName":"Josh Johnson"}},{"identifier":{"id":"hashicorp.sentinel","uuid":"287ef70d-bc55-4f6a-b852-57e627638836"},"version":"0.2.2","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/hashicorp.sentinel-0.2.2","scheme":"file"},"relativeLocation":"hashicorp.sentinel-0.2.2","metadata":{"id":"287ef70d-bc55-4f6a-b852-57e627638836","publisherId":"a8dd781d-e144-400a-943c-417165981be2","publisherDisplayName":"HashiCorp","targetPlatform":"undefined","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1668453957123,"preRelease":false}},{"identifier":{"id":"kiteco.kite","uuid":"d697a7e8-00fa-4039-9067-4b69a9a90f6e"},"version":"0.147.0","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/kiteco.kite-0.147.0","scheme":"file"},"relativeLocation":"kiteco.kite-0.147.0","metadata":{"id":"d697a7e8-00fa-4039-9067-4b69a9a90f6e","publisherId":"202e7bef-8dda-4cf3-89b7-0df74948ab8c","publisherDisplayName":"Kite","installedTimestamp":1626957645488}},{"identifier":{"id":"micnil.vscode-checkpoints","uuid":"5b7424e4-d934-4816-83ce-b422c482a9e7"},"version":"1.3.3","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/micnil.vscode-checkpoints-1.3.3","scheme":"file"},"relativeLocation":"micnil.vscode-checkpoints-1.3.3","metadata":{"id":"5b7424e4-d934-4816-83ce-b422c482a9e7","publisherId":"f8a43d30-88c0-44f4-b306-65396ce81631","publisherDisplayName":"Michael Nilsson","targetPlatform":"undefined","updated":true,"isPreReleaseVersion":false,"preRelease":false,"installedTimestamp":1652723218079}},{"identifier":{"id":"mohsen1.prettify-json","uuid":"67e66172-30c7-4478-8f5d-6eac4ae755dc"},"version":"0.0.3","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/mohsen1.prettify-json-0.0.3","scheme":"file"},"relativeLocation":"mohsen1.prettify-json-0.0.3","metadata":{"id":"67e66172-30c7-4478-8f5d-6eac4ae755dc","publisherId":"114b20ca-e58f-4673-9024-1fe88a3e941a","publisherDisplayName":"Mohsen Azimi"}},{"identifier":{"id":"redhat.vscode-commons","uuid":"2f0eaac2-070b-4dc7-9b23-8dd4c970c11c"},"version":"0.0.6","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/redhat.vscode-commons-0.0.6","scheme":"file"},"relativeLocation":"redhat.vscode-commons-0.0.6","metadata":{"id":"2f0eaac2-070b-4dc7-9b23-8dd4c970c11c","publisherId":"eed56242-9699-4317-8bc7-e9f4b9bdd3ff","publisherDisplayName":"Red Hat","installedTimestamp":1621512717842}},{"identifier":{"id":"sf-infosec.infosec-aws-templates"},"version":"0.0.1","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/sf-infosec.infosec-aws-templates-0.0.1","scheme":"file"},"relativeLocation":"sf-infosec.infosec-aws-templates-0.0.1","metadata":{}},{"identifier":{"id":"tht13.rst-vscode","uuid":"9a76007e-6367-44f0-b175-2439b4e81196"},"version":"3.0.1","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/tht13.rst-vscode-3.0.1","scheme":"file"},"relativeLocation":"tht13.rst-vscode-3.0.1","metadata":{"id":"9a76007e-6367-44f0-b175-2439b4e81196","publisherId":"78ff7982-87b9-4f5c-8886-f79f581462f0","publisherDisplayName":"Thomas Haakon Townsend"}},{"identifier":{"id":"vscjava.vscode-java-dependency","uuid":"7865e561-1c83-410e-9b99-aabada597a7e"},"version":"0.21.1","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/vscjava.vscode-java-dependency-0.21.1","scheme":"file"},"relativeLocation":"vscjava.vscode-java-dependency-0.21.1","metadata":{"id":"7865e561-1c83-410e-9b99-aabada597a7e","publisherId":"bae08b87-578e-41ec-ab1c-0b036e7add88","publisherDisplayName":"Microsoft","targetPlatform":"undefined","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1667287341686,"preRelease":false}},{"identifier":{"id":"vscjava.vscode-java-pack","uuid":"96f11e1f-1a46-4592-b084-f025b2c2a81f"},"version":"0.25.7","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/vscjava.vscode-java-pack-0.25.7","scheme":"file"},"relativeLocation":"vscjava.vscode-java-pack-0.25.7","metadata":{"id":"96f11e1f-1a46-4592-b084-f025b2c2a81f","publisherId":"bae08b87-578e-41ec-ab1c-0b036e7add88","publisherDisplayName":"Microsoft","targetPlatform":"undefined","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1669714007977,"preRelease":false}},{"identifier":{"id":"vscjava.vscode-java-test","uuid":"67c06b0d-1891-42ca-b2a8-113e79bff069"},"version":"0.37.1","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/vscjava.vscode-java-test-0.37.1","scheme":"file"},"relativeLocation":"vscjava.vscode-java-test-0.37.1","metadata":{"id":"67c06b0d-1891-42ca-b2a8-113e79bff069","publisherId":"bae08b87-578e-41ec-ab1c-0b036e7add88","publisherDisplayName":"Microsoft","targetPlatform":"undefined","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"preRelease":false,"installedTimestamp":1662467993062}},{"identifier":{"id":"hashicorp.terraform","uuid":"4a23294b-fd16-4c51-9759-da9936474cf8"},"version":"2.25.2","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/hashicorp.terraform-2.25.2-win32-x64","scheme":"file"},"relativeLocation":"hashicorp.terraform-2.25.2-win32-x64","metadata":{"id":"4a23294b-fd16-4c51-9759-da9936474cf8","publisherId":"a8dd781d-e144-400a-943c-417165981be2","publisherDisplayName":"HashiCorp","targetPlatform":"win32-x64","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1671137758849,"preRelease":false}},{"identifier":{"id":"ms-azuretools.vscode-docker","uuid":"0479fc1c-3d67-49f9-b087-fb9069afe48f"},"version":"1.23.3","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/ms-azuretools.vscode-docker-1.23.3","scheme":"file"},"relativeLocation":"ms-azuretools.vscode-docker-1.23.3","metadata":{"id":"0479fc1c-3d67-49f9-b087-fb9069afe48f","publisherId":"52b787f2-79a9-4f32-99b4-393afe3005d3","publisherDisplayName":"Microsoft","targetPlatform":"undefined","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1671482130574,"preRelease":false}},{"identifier":{"id":"visualstudioexptteam.vscodeintellicode","uuid":"876e8f93-74d0-4f4f-91b7-34a09f19f444"},"version":"1.2.30","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/visualstudioexptteam.vscodeintellicode-1.2.30","scheme":"file"},"relativeLocation":"visualstudioexptteam.vscodeintellicode-1.2.30","metadata":{"id":"876e8f93-74d0-4f4f-91b7-34a09f19f444","publisherId":"e8db1608-52e8-4d8d-92a6-779c5db302a9","publisherDisplayName":"Microsoft","targetPlatform":"undefined","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1673230776114,"preRelease":false}},{"identifier":{"id":"redhat.vscode-yaml","uuid":"2061917f-f76a-458a-8da9-f162de22b97e"},"version":"1.11.0","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/redhat.vscode-yaml-1.11.0","scheme":"file"},"relativeLocation":"redhat.vscode-yaml-1.11.0","metadata":{"id":"2061917f-f76a-458a-8da9-f162de22b97e","publisherId":"eed56242-9699-4317-8bc7-e9f4b9bdd3ff","publisherDisplayName":"Red Hat","targetPlatform":"undefined","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1673273978058,"preRelease":false}},{"identifier":{"id":"redhat.java","uuid":"198a707e-28af-4e84-8610-6e2f628dd12d"},"version":"1.14.0","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/redhat.java-1.14.0-win32-x64","scheme":"file"},"relativeLocation":"redhat.java-1.14.0-win32-x64","metadata":{"id":"198a707e-28af-4e84-8610-6e2f628dd12d","publisherId":"eed56242-9699-4317-8bc7-e9f4b9bdd3ff","publisherDisplayName":"Red Hat","targetPlatform":"win32-x64","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1674007472628,"preRelease":false}},{"identifier":{"id":"vscjava.vscode-maven","uuid":"b0f06c6b-24fb-4d7b-bd79-bc5e2fa17312"},"version":"0.40.4","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/vscjava.vscode-maven-0.40.4","scheme":"file"},"relativeLocation":"vscjava.vscode-maven-0.40.4","metadata":{"id":"b0f06c6b-24fb-4d7b-bd79-bc5e2fa17312","publisherId":"bae08b87-578e-41ec-ab1c-0b036e7add88","publisherDisplayName":"Microsoft","targetPlatform":"undefined","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1674143702618,"preRelease":false}},{"identifier":{"id":"ms-vscode.powershell","uuid":"40d39ce9-c381-47a0-80c8-a6661f731eab"},"version":"2023.1.0","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/ms-vscode.powershell-2023.1.0","scheme":"file"},"relativeLocation":"ms-vscode.powershell-2023.1.0","metadata":{"id":"40d39ce9-c381-47a0-80c8-a6661f731eab","publisherId":"5f5636e7-69ed-4afe-b5d6-8d231fb3d3ee","publisherDisplayName":"Microsoft","targetPlatform":"undefined","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1674220474299,"preRelease":false}},{"identifier":{"id":"visualstudioexptteam.intellicode-api-usage-examples","uuid":"9fa2a00e-3bfa-4c2a-abc4-a865bb2b5cf3"},"version":"0.2.7","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/visualstudioexptteam.intellicode-api-usage-examples-0.2.7","scheme":"file"},"relativeLocation":"visualstudioexptteam.intellicode-api-usage-examples-0.2.7","metadata":{"id":"9fa2a00e-3bfa-4c2a-abc4-a865bb2b5cf3","publisherId":"e8db1608-52e8-4d8d-92a6-779c5db302a9","publisherDisplayName":"Microsoft","targetPlatform":"undefined","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1674710288141,"preRelease":false}},{"identifier":{"id":"vscjava.vscode-java-debug","uuid":"61fcd0cf-64d7-4836-8d6b-d55f4fb83281"},"version":"0.48.0","location":{"$mid":1,"path":"/c:/Users/bqd4/.vscode/extensions/vscjava.vscode-java-debug-0.48.0","scheme":"file"},"relativeLocation":"vscjava.vscode-java-debug-0.48.0","metadata":{"id":"61fcd0cf-64d7-4836-8d6b-d55f4fb83281","publisherId":"bae08b87-578e-41ec-ab1c-0b036e7add88","publisherDisplayName":"Microsoft","targetPlatform":"undefined","isApplicationScoped":false,"updated":true,"isPreReleaseVersion":false,"installedTimestamp":1675244510317,"preRelease":false}}]

After adding "extensions.verifySignature,": false to the top of my C:\Users\bqd4\AppData\Roaming\Code\User\settings.json, installing the python extension works in VS Code 1.75.0:
2023-02-10 07:29:01.915 [info] Deleted from disk ms-toolsai.jupyter-keymap c:\Users\bqd4\.vscode\extensions\ms-toolsai.jupyter-keymap-1.0.0
2023-02-10 07:29:02.020 [info] Deleted from disk ms-toolsai.vscode-jupyter-slideshow c:\Users\bqd4\.vscode\extensions\ms-toolsai.vscode-jupyter-slideshow-0.1.5
2023-02-10 07:29:02.118 [info] Deleted from disk ms-toolsai.jupyter-renderers c:\Users\bqd4\.vscode\extensions\ms-toolsai.jupyter-renderers-1.0.14
2023-02-10 07:29:02.248 [info] Deleted from disk ms-toolsai.vscode-jupyter-cell-tags c:\Users\bqd4\.vscode\extensions\ms-toolsai.vscode-jupyter-cell-tags-0.1.6
2023-02-10 07:29:02.457 [info] Starting worker process with pid 26752 (type: fileWatcher, window: 1).
2023-02-10 07:29:03.202 [info] Deleted from disk dbaeumer.vscode-eslint c:\Users\bqd4\.vscode\extensions\dbaeumer.vscode-eslint-2.4.0
2023-02-10 07:29:03.237 [info] Deleted from disk ms-toolsai.jupyter c:\Users\bqd4\.vscode\extensions\ms-toolsai.jupyter-2022.9.1303220346
2023-02-10 07:29:03.729 [info] Deleted from disk ms-python.isort c:\Users\bqd4\.vscode\extensions\ms-python.isort-2022.8.0
2023-02-10 07:29:03.963 [info] Deleted from disk ms-python.vscode-pylance c:\Users\bqd4\.vscode\extensions\ms-python.vscode-pylance-2023.1.10
2023-02-10 07:29:08.331 [info] Deleted from disk ms-python.python c:\Users\bqd4\.vscode\extensions\ms-python.python-2022.18.2
2023-02-10 07:29:20.805 [info] Getting Manifest... ms-python.python
2023-02-10 07:29:20.809 [info] Installing extension: ms-python.python
2023-02-10 07:29:22.083 [info] Getting Manifest... ms-toolsai.jupyter
2023-02-10 07:29:22.374 [info] Getting Manifest... ms-toolsai.jupyter-keymap
2023-02-10 07:29:22.479 [info] Getting Manifest... ms-toolsai.jupyter-renderers
2023-02-10 07:29:22.561 [info] Getting Manifest... ms-toolsai.vscode-jupyter-cell-tags
2023-02-10 07:29:22.599 [info] Getting Manifest... ms-toolsai.vscode-jupyter-slideshow
2023-02-10 07:29:22.691 [info] Getting Manifest... ms-python.vscode-pylance
2023-02-10 07:29:22.731 [info] Getting Manifest... ms-python.isort
2023-02-10 07:29:22.914 [info] Installing extension: ms-toolsai.jupyter ms-python.python
2023-02-10 07:29:22.914 [info] Installing extension: ms-toolsai.jupyter-keymap ms-python.python
2023-02-10 07:29:22.914 [info] Installing extension: ms-toolsai.jupyter-renderers ms-python.python
2023-02-10 07:29:22.915 [info] Installing extension: ms-toolsai.vscode-jupyter-cell-tags ms-python.python
2023-02-10 07:29:22.915 [info] Installing extension: ms-toolsai.vscode-jupyter-slideshow ms-python.python
2023-02-10 07:29:22.915 [info] Installing extension: ms-python.vscode-pylance ms-python.python
2023-02-10 07:29:22.915 [info] Installing extension: ms-python.isort ms-python.python
2023-02-10 07:29:23.460 [info] Extracted extension to c:\Users\bqd4\.vscode\extensions\.2442b419-3e76-425e-be82-165d664875c9: ms-toolsai.jupyter-keymap
2023-02-10 07:29:23.507 [info] Extracted extension to c:\Users\bqd4\.vscode\extensions\.54547ef1-6461-439c-8c1a-cd8ce2386cea: ms-toolsai.vscode-jupyter-slideshow
2023-02-10 07:29:23.527 [info] Renamed to c:\Users\bqd4\.vscode\extensions\ms-toolsai.vscode-jupyter-slideshow-0.1.5
2023-02-10 07:29:23.529 [info] Extracted extension to c:\Users\bqd4\.vscode\extensions\.b3fd8c96-9a53-4cd2-8f53-d7460f003be8: ms-toolsai.vscode-jupyter-cell-tags
2023-02-10 07:29:23.536 [info] Extracting completed. ms-toolsai.vscode-jupyter-slideshow
2023-02-10 07:29:23.546 [info] Renamed to c:\Users\bqd4\.vscode\extensions\ms-toolsai.vscode-jupyter-cell-tags-0.1.6
2023-02-10 07:29:23.556 [info] Extracting completed. ms-toolsai.vscode-jupyter-cell-tags
2023-02-10 07:29:24.605 [info] Extracted extension to c:\Users\bqd4\.vscode\extensions\.4d35c39a-0e1b-4072-81c9-634f2252194d: ms-toolsai.jupyter-renderers
2023-02-10 07:29:24.632 [info] Renamed to c:\Users\bqd4\.vscode\extensions\ms-toolsai.jupyter-renderers-1.0.14
2023-02-10 07:29:24.650 [info] Extracting completed. ms-toolsai.jupyter-renderers
2023-02-10 07:29:25.320 [info] Renamed to c:\Users\bqd4\.vscode\extensions\ms-toolsai.jupyter-keymap-1.0.0
2023-02-10 07:29:25.458 [info] Extracted extension to c:\Users\bqd4\.vscode\extensions\.183b9b16-1a49-405c-b111-15d8cd49d28c: ms-toolsai.jupyter
2023-02-10 07:29:25.503 [info] Renamed to c:\Users\bqd4\.vscode\extensions\ms-toolsai.jupyter-2023.1.2010391206
2023-02-10 07:29:25.586 [info] Extracting completed. ms-toolsai.jupyter
2023-02-10 07:29:26.508 [info] Extracting completed. ms-toolsai.jupyter-keymap
2023-02-10 07:29:31.901 [info] Extracted extension to c:\Users\bqd4\.vscode\extensions\.ee8b332e-c237-4a67-a553-9d533b8804b1: ms-python.python
2023-02-10 07:29:32.775 [info] Renamed to c:\Users\bqd4\.vscode\extensions\ms-python.python-2023.2.0
2023-02-10 07:29:33.056 [info] Extracting completed. ms-python.python
2023-02-10 07:29:34.666 [error] RequestService#request (browser) - error https://ms-python.gallery.vsassets.io/_apis/public/gallery/publisher/ms-python/extension/vscode-pylance/2023.2.20/assetbyname/Microsoft.VisualStudio.Services.VSIXPackage?redirect=true&install=true {}
2023-02-10 07:29:35.640 [info] Extracted extension to c:\Users\bqd4\.vscode\extensions\.7b862d10-9f89-4dd1-9ed9-5fd1d9bf37cc: ms-python.isort
2023-02-10 07:29:35.664 [info] Renamed to c:\Users\bqd4\.vscode\extensions\ms-python.isort-2022.8.0
2023-02-10 07:29:35.687 [info] Extracting completed. ms-python.isort
2023-02-10 07:29:48.227 [info] Extracted extension to c:\Users\bqd4\.vscode\extensions\.ecdb6d13-3193-42ff-b2e2-28519589fe4a: ms-python.vscode-pylance
2023-02-10 07:29:48.999 [info] Renamed to c:\Users\bqd4\.vscode\extensions\ms-python.vscode-pylance-2023.2.20
2023-02-10 07:29:49.238 [info] Extracting completed. ms-python.vscode-pylance
2023-02-10 07:29:49.268 [info] Extension installed successfully: ms-toolsai.vscode-jupyter-slideshow
2023-02-10 07:29:49.268 [info] Extension installed successfully: ms-toolsai.vscode-jupyter-cell-tags
2023-02-10 07:29:49.268 [info] Extension installed successfully: ms-toolsai.jupyter-renderers
2023-02-10 07:29:49.268 [info] Extension installed successfully: ms-toolsai.jupyter
2023-02-10 07:29:49.269 [info] Extension installed successfully: ms-toolsai.jupyter-keymap
2023-02-10 07:29:49.269 [info] Extension installed successfully: ms-python.python
2023-02-10 07:29:49.269 [info] Extension installed successfully: ms-python.isort
2023-02-10 07:29:49.269 [info] Extension installed successfully: ms-python.vscode-pylance

As a final test, I removed the "extensions.verifySignature,": false from the top of my C:\Users\bqd4\AppData\Roaming\Code\User\settings.json and installed VS Code 1.75.1.
So, your theory seems to be correct.

@isidorn There is an error while signature verification -  UnhandledException: Signature: UnhandledException - Is this a known issue?
@huhqwerty Thanks for trying out and providing necessary information. Until we analyse and fix this, I would recommend to use this setting "extensions.verifySignature": false in two files

User Settings file - C:\Users\bqd4\AppData\Roaming\Code\User\settings.json
Remote Settings file - You can open this file from the settings UI.

@sandy081 looks like a new issue to me
@huhqwerty just to be 100% certain, can you reproduce with latest 1.75.1 version?
@dtivel

@isidorn yes, see above failed result of installing python extension using 1.75.1 version of VS Code.  I then added "extensions.verifySignature": false, to the top of my C:\Users\bqd4\AppData\Roaming\Code\User\settings.json, restarted VS Code, and successfully installed the python extension.

1.75.1 fixed Untrusted error on Linux, but this issue is different:  UnhandledException on Windows.
I'm working on adding additional logging here which should help get to the root cause.

Just chiming in as a plus 1 for this issue. Like simonamc, this started for me when I discovered and experimented with WSL & dev containers. Seems like too much of a coincidence to not be related?
I'm happy to collect and share logs if its any help beyond what the others have already shared. Just let me know.
Here are a couple notes in case its helpful:

the issue does not go away if I run vscode with extensions disabled
I am able to install / update most extensions manually (by downloading *.vsix). The exception is Python (ms-python.python), which seems to have been removed and cannot be installed.

I am using v1.75.1.
thanks,

Facing similar issue - terminal log shows [error] UnhandledException: Signature: UnhandledException

@rbharathkumar, it sounds like the error appears inconsistently.  Is this true or between the two installs (1 with error and 1 without) did you disable verification?  Also, is the install on Windows?
@geoffdudds, is the failed install on Windows or in a container or both?

the issue does not go away if I run vscode with extensions disabled

Just so I understand, you launch VS Code with --disable-extensions, then try to install the extension that failed, and installation fails in the same way?  Are there any successful extension installations when verification is enabled?

I am able to install / update most extensions manually (by downloading *.vsix). The exception is Python (ms-python.python), which seems to have been removed and cannot be installed.

Is Python still unavailable for you?  I see version v2023.2.0:

@dtivel the failed install is on windows only.
I just confirmed I can install ms-python.python and update other extensions in my dev container.
I start vscode, then run Developer: Reload with Extensions Disabled from the command palette. When it reloads, there is a popup in the corner saying All installed extensions are temporarily disabled. From here there are currently three extensions that need updating - Dev Containers, GitHub Pull Requests, and Jupyter. All fail to update when I select "Update" from the extension side panel. All three were successful when installed manually by downloading the vsix.
Here are some I am able to install from the side panel:

TabOut (albert.tabout)
.run (formulahendry.code-runner)
Highlight (fabiospampinato.vscode-highlight)
Inno Setup (chouzz.vscode-innosetup)

Note that the above four examples were successful whether extensions were disabled or not.
It seems I can install the ms-python.python in windows now. But I still had to install manually.
Ok, so after writing all that, I added the disable verification to my settings.json file, then uninstalled / reinstalled Dev Containers. As expected, it worked. But to my surprise, if I remove the disable verification, I am now still able to uninstall and reinstall. I don't understand how to consistently reproduce this issue. Sorry, this is no longer a very helpful post but I'll post anyways in case there is something of use for you.

@rbharathkumar, it sounds like the error appears inconsistently. Is this true or between the two installs (1 with error and 1 without) did you disable verification? Also, is the install on Windows?

Hi @dtivel , Thank you for your response.
I originally tried to install the sqltools extension
I received the error. Alongside it I also received error stating several of my extensions including pylance, python were not getting updated. So removed all the extensions that were giving error. Tried again - similar issue. The next day, sqltools extension installed without any issue. When I tried to install mssql extension, it failed again with same signature issue.
As per your suggestion, added the line - "extensions.verifySignature": false to the settings.json file and was able to install the mssql extension without any issue. But I would prefer to have the verification enabled.
Environment:
Version: 1.75.1 (user setup)
Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf
Date: 2023-02-08T21:32:34.589Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045
Sandboxed: No

Has similar problem in Windows platform, VS Code Version is 1.75.1. I have didn't use my laptop for around one month. When I came back and upgrade VS Code to this version, some extension can't install or update automatically. Use VSIX to install, update manually or add "extensions.verifySignature": false in settings.json is works for me.
[error] Untrusted: Signature: Untrusted     at yt.download (vscode-file://vscode-app/d:/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:62:17985)     at async $.h (vscode-file://vscode-app/d:/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:90:171351)
2023-02-19 20:51:47.628 [info] Getting Manifest... ms-vscode-remote.remote-containers 2023-02-19 20:51:47.632 [info] Installing extension: ms-vscode-remote.remote-containers 2023-02-19 20:51:47.633 [error] [uncaught exception in sharedProcess]: Untrusted: Signature: Untrusted     at yt.download (vscode-file://vscode-app/d:/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:62:17985)     at async $.h (vscode-file://vscode-app/d:/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:90:171351) 2023-02-19 20:51:47.917 [error] Error while installing the extension: ms-vscode-remote.remote-containers 2023-02-19 20:51:47.918 [error] Failed to install extension. ms-vscode-remote.remote-containers 2023-02-19 20:51:47.918 [error] Signature: Untrusted     at yt.download (vscode-file://vscode-app/d:/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:62:17985)     at async $.h (vscode-file://vscode-app/d:/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:90:171351)

We have added diagnostics to help us diagnose this issue, but moving to next milestone since I expect we push a fix in March.

Here you go.  Installed the current Insiders version of VS Code and set the Log level to Trace.  Then tried to install the Release version of the Python extension.
2023-02-23 11:07:30.758 [trace] Extension signature verification details for ms-toolsai.jupyter-keymap 1.0.0:
Package file size:  79765
Signature archive file size:  17624
Exit code:  SignatureArchiveIsInvalidZip

2023-02-23 11:07:30.758 [trace] Extension signature verification details for ms-toolsai.vscode-jupyter-slideshow 0.1.5:
Package file size:  147940
Signature archive file size:  17644
Exit code:  SignatureArchiveIsInvalidZip

2023-02-23 11:07:30.763 [error] Error while installing the extension: ms-toolsai.vscode-jupyter-slideshow
2023-02-23 11:07:30.765 [error] Error while installing the extension: ms-toolsai.jupyter-keymap
2023-02-23 11:07:30.766 [error] [uncaught exception in sharedProcess]: end of central directory record signature not found: CorruptZip: end of central directory record signature not found
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:223)
    at async X.x (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:20760)
    at async X.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:18897)
2023-02-23 11:07:30.766 [error] [uncaught exception in sharedProcess]: end of central directory record signature not found: CorruptZip: end of central directory record signature not found
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:223)
    at async X.x (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:20760)
    at async X.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:18897)
2023-02-23 11:07:31.000 [trace] ExtensionGalleryService#downloadSignatureArchive ms-toolsai.jupyter-renderers
2023-02-23 11:07:31.000 [trace] Using main request service
2023-02-23 11:07:31.022 [trace] Extension signature verification details for ms-toolsai.vscode-jupyter-cell-tags 0.1.6:
Package file size:  157684
Signature archive file size:  17644
Exit code:  SignatureArchiveIsInvalidZip

2023-02-23 11:07:31.027 [error] Error while installing the extension: ms-toolsai.vscode-jupyter-cell-tags
2023-02-23 11:07:31.029 [error] [uncaught exception in sharedProcess]: end of central directory record signature not found: CorruptZip: end of central directory record signature not found
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:223)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async X.x (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:20760)
    at async X.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:18897)
2023-02-23 11:07:31.431 [trace] Using main request service
2023-02-23 11:07:31.983 [trace] ExtensionGalleryService#downloadSignatureArchive ms-toolsai.jupyter
2023-02-23 11:07:31.983 [trace] Using main request service
2023-02-23 11:07:32.706 [trace] Using main request service
2023-02-23 11:07:32.820 [trace] Extension signature verification details for ms-toolsai.jupyter-renderers 1.0.15:
Package file size:  7956952
Signature archive file size:  17632
Exit code:  SignatureArchiveIsInvalidZip

2023-02-23 11:07:32.822 [error] Error while installing the extension: ms-toolsai.jupyter-renderers
2023-02-23 11:07:32.823 [error] [uncaught exception in sharedProcess]: end of central directory record signature not found: CorruptZip: end of central directory record signature not found
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:223)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async X.x (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:20760)
    at async X.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:18897)
2023-02-23 11:07:33.395 [trace] Extension signature verification details for ms-toolsai.jupyter 2023.1.2010391206:
Package file size:  13234950
Signature archive file size:  17634
Exit code:  SignatureArchiveIsInvalidZip

2023-02-23 11:07:33.397 [error] Error while installing the extension: ms-toolsai.jupyter
2023-02-23 11:07:33.398 [error] [uncaught exception in sharedProcess]: end of central directory record signature not found: CorruptZip: end of central directory record signature not found
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:223)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async X.x (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:20760)
    at async X.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:18897)
2023-02-23 11:07:35.346 [trace] ExtensionGalleryService#downloadSignatureArchive ms-python.python
2023-02-23 11:07:35.346 [trace] Using main request service
2023-02-23 11:07:35.625 [trace] Using main request service
2023-02-23 11:07:36.943 [trace] Extension signature verification details for ms-python.python 2023.2.0:
Package file size:  15139011
Signature archive file size:  17610
Exit code:  SignatureArchiveIsInvalidZip

2023-02-23 11:07:36.947 [error] Error while installing the extension: ms-python.python
2023-02-23 11:07:36.948 [error] Failed to install extension. ms-python.python
2023-02-23 11:07:36.949 [error] Error: end of central directory record signature not found,end of central directory record signature not found,end of central directory record signature not found,end of central directory record signature not found,end of central directory record signature not found,end of central directory record signature not found
    at vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:88:89716
    at Array.reduce (<anonymous>)
    at E (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:88:89702)
    at W.D (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:88:81056)
    at async W.z (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:88:78569)
    at async W.installFromGallery (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:88:75037)
2023-02-23 11:07:36.950 [error] [uncaught exception in sharedProcess]: end of central directory record signature not found: CorruptZip: end of central directory record signature not found
    at yt.download (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:223)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async X.x (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:20760)
    at async X.h (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code%20Insiders/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:18897)

@huhqwerty, thanks so much for providing this information.  I've been trying to make sense of the information you provided.
In short, VS Code downloads 2 files from VS Marketplace:  the extension package file and a signature archive file.  From the information you've provided, it looks like the extension package files downloaded completely, but each signature archive file downloaded ~17.6 KB, even if the actual signature archive file is smaller!

Someone suggested to me that the Electron (Chromium) network layer may be caching data because of cache headers in the response.  A quick test to see if this is the issue would be to start VS Code using a new user data directory:
code --user-data-dir <directory>

Can you please try this and see if the same extension installation succeeds or fails with a new user data directory?

I changed C:\Users\bqd4\AppData\Roaming\Code\User\settings.json back to "extensions.verifySignature": true, and started VS Code with code --user-data-dir C:\DEV\vscode_data_dir .
I uninstalled the python extension and installed it again.  This is using VS Code 1.75.1.  It still fails:
2023-03-01 08:47:19.223 [warning] Via 'product.json#extensionEnabledApiProposals' extension 'github.vscode-pull-request-github' wants API proposal 'commentsResolvedState' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2023-03-01 08:47:19.978 [warning] [redhat.vscode-yaml]: Cannot register 'redhat.telemetry.enabled'. This property is already registered.
2023-03-01 08:47:22.817 [info] [perf] Render performance baseline is 161ms
2023-03-01 08:48:13.876 [error] Error: UnhandledException,UnhandledException,UnhandledException,UnhandledException,UnhandledException,UnhandledException
    at vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89578
    at Array.reduce (<anonymous>)
    at E (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89564)
    at ne.D (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:80916)
    at async ne.z (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:78417)
    at async ne.installFromGallery (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:74855)
2023-03-01 08:48:13.960 [error] UnhandledException,UnhandledException,UnhandledException,UnhandledException,UnhandledException,UnhandledException: Error: UnhandledException,UnhandledException,UnhandledException,UnhandledException,UnhandledException,UnhandledException
    at vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89578
    at Array.reduce (<anonymous>)
    at E (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:89564)
    at ne.D (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:80916)
    at async ne.z (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:78417)
    at async ne.installFromGallery (vscode-file://vscode-app/c:/DEV/Applications/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:88:74855)

After set Log level with trace:
2023-03-03 20:37:40.451 [trace] CommandService#executeCommand workbench.output.action.clearOutput
2023-03-03 20:37:45.925 [trace] RequestService#request (browser) - begin https://ms-azuretools.gallerycdn.vsassets.io/extensions/ms-azuretools/vscode-docker/1.24.0/1677187109445/Microsoft.VisualStudio.Code.Manifest
2023-03-03 20:37:45.936 [trace] RequestService#request (browser) - success https://ms-azuretools.gallerycdn.vsassets.io/extensions/ms-azuretools/vscode-docker/1.24.0/1677187109445/Microsoft.VisualStudio.Code.Manifest
2023-03-03 20:37:46.722 [error] Signature: Untrusted
at yt.download (vscode-file://vscode-app/d:/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:468)
at async X.x (vscode-file://vscode-app/d:/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:20760)
at async X.h (vscode-file://vscode-app/d:/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:18897)
2023-03-03 20:37:46.767 [error] Untrusted: Signature: Untrusted
at yt.download (vscode-file://vscode-app/d:/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:468)
at async X.x (vscode-file://vscode-app/d:/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:20760)
at async X.h (vscode-file://vscode-app/d:/Microsoft%20VS%20Code/resources/app/out/vs/code/node/sharedProcess/sharedProcessMain.js:91:18897)
2023-03-03 20:37:51.541 [trace] CommandService#executeCommand notification.clear
2023-03-03 20:38:07.260 [trace] CommandService#executeCommand _update.state
2023-03-03 20:38:07.512 [trace] [File Watcher (node.js)] [raw] ["change"] globalStorage
2023-03-03 20:38:07.512 [trace] [File Watcher (node.js)] [CHANGED]
c:\Users\a\AppData\Roaming\Code\User\globalStorage
2023-03-03 20:38:07.512 [trace] [File Watcher (node.js)] [raw] ["change"] globalStorage
2023-03-03 20:38:07.513 [trace] [File Watcher (node.js)] [CHANGED]
c:\Users\a\AppData\Roaming\Code\User\globalStorage
2023-03-03 20:38:07.587 [trace] [File Watcher (node.js)] >> normalized [CHANGED] c:\Users\a\AppData\Roaming\Code\User\globalStorage
2023-03-03 20:38:07.587 [debug] User data changed
2023-03-03 20:38:28.336 [trace] CommandService#executeCommand _setContext
2023-03-03 20:38:28.640 [trace] MainThreadTreeViews#$refresh sqltoolsViewConnectionExplorer undefined
2023-03-03 20:38:28.895 [trace] MainThreadTreeViews#$refresh sqltoolsViewConnectionExplorer undefined
2023-03-03 20:38:29.114 [error] Cannot read properties of undefined (reading 'document'): TypeError: Cannot read properties of undefined (reading 'document')
at c:\Users\a.vscode\extensions\mtxr.sqltools-0.27.1\dist\extension.js:1:79096
at f.invoke (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:145)
at g.deliver (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2066)
at h.fire (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1704)
at y.$acceptEditorPropertiesChanged (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:98:155515)
at c.N (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:11223)
at c.M (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:10941)
at c.H (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:10034)
at c.G (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:9015)
at d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:7803
at f.invoke (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:145)
at g.deliver (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2066)
at h.fire (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1704)
at p.fire (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:72:14907)
at d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:122:16556
at f.invoke (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:145)
at g.deliver (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2066)
at h.fire (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1704)
at p.fire (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:72:14907)
at MessagePortMain. (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:122:14682)
at MessagePortMain.emit (node:events:526:28)
at Object.MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:5:364)
2023-03-03 20:38:29.205 [trace] MainThreadTreeViews#$refresh sqltoolsViewConnectionExplorer undefined
2023-03-03 20:38:29.414 [trace] MainThreadTreeViews#$refresh sqltoolsViewConnectionExplorer undefined
2023-03-03 20:38:37.267 [trace] CommandService#executeCommand _update.state
2023-03-03 20:38:37.521 [trace] [File Watcher (node.js)] [raw] ["change"] globalStorage
2023-03-03 20:38:37.521 [trace] [File Watcher (node.js)] [CHANGED]
c:\Users\a\AppData\Roaming\Code\User\globalStorage
2023-03-03 20:38:37.521 [trace] [File Watcher (node.js)] [raw] ["change"] globalStorage
2023-03-03 20:38:37.522 [trace] [File Watcher (node.js)] [CHANGED]
c:\Users\a\AppData\Roaming\Code\User\globalStorage
2023-03-03 20:38:37.595 [trace] [File Watcher (node.js)] >> normalized [CHANGED] c:\Users\a\AppData\Roaming\Code\User\globalStorage
2023-03-03 20:38:37.595 [debug] User data changed
2023-03-03 20:38:37.737 [error] Cannot read properties of undefined (reading 'document'): TypeError: Cannot read properties of undefined (reading 'document')
at c:\Users\a.vscode\extensions\mtxr.sqltools-0.27.1\dist\extension.js:1:79096
at f.invoke (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:145)
at g.deliver (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2066)
at h.fire (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1704)
at y.$acceptEditorPropertiesChanged (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:98:155515)
at c.N (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:11223)
at c.M (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:10941)
at c.H (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:10034)
at c.G (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:9015)
at d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:7803
at f.invoke (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:145)
at g.deliver (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2066)
at h.fire (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1704)
at p.fire (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:72:14907)
at d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:122:16556
at f.invoke (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:145)
at g.deliver (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2066)
at h.fire (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1704)
at p.fire (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:72:14907)
at MessagePortMain. (d:\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:122:14682)
at MessagePortMain.emit (node:events:526:28)
at Object.MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:5:364)
2023-03-03 20:38:59.595 [trace] CommandService#executeCommand _setContext
2023-03-03 20:38:59.626 [trace] CommandService#executeCommand _setContext
vscode version:
1.76.0 (system setup)
submit: 92da9481c0904c6adfe372c12da3b7748d74bdcb
date: 2023-03-01T10:22:44.506Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045

FYI, I continue to have this issue with VS Code:
Version: 1.77.3 (user setup)
Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710
Date: 2023-04-12T09:16:02.548Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045
Sandboxed: Yes
2023-04-19 10:53:03.993 [info] Installing extension: ms-python.vscode-pylance ms-python.python
2023-04-19 10:53:05.781 [error] Error while installing the extension: ms-toolsai.jupyter-renderers
2023-04-19 10:53:05.785 [error] [uncaught exception in sharedProcess]: end of central directory record signature not found: CorruptZip: end of central directory record signature not found
    at yt.download (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:141)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async j.y (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:20893)
    at async j.h (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:18962)
2023-04-19 10:53:05.803 [error] Error while installing the extension: ms-toolsai.vscode-jupyter-cell-tags
2023-04-19 10:53:05.804 [error] [uncaught exception in sharedProcess]: end of central directory record signature not found: CorruptZip: end of central directory record signature not found
    at yt.download (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:141)
    at async j.y (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:20893)
    at async j.h (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:18962)
2023-04-19 10:53:05.815 [error] Error while installing the extension: ms-toolsai.jupyter-keymap
2023-04-19 10:53:05.816 [error] [uncaught exception in sharedProcess]: end of central directory record signature not found: CorruptZip: end of central directory record signature not found
    at yt.download (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:141)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async j.y (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:20893)
    at async j.h (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:18962)
2023-04-19 10:53:05.882 [error] Error while installing the extension: ms-toolsai.jupyter
2023-04-19 10:53:05.883 [error] [uncaught exception in sharedProcess]: end of central directory record signature not found: CorruptZip: end of central directory record signature not found
    at yt.download (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:141)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async j.y (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:20893)
    at async j.h (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:18962)
2023-04-19 10:53:05.897 [error] Error while installing the extension: ms-python.python
2023-04-19 10:53:05.897 [error] [uncaught exception in sharedProcess]: end of central directory record signature not found: CorruptZip: end of central directory record signature not found
    at yt.download (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:141)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async j.y (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:20893)
    at async j.h (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:18962)
2023-04-19 10:53:05.962 [error] Error while installing the extension: ms-toolsai.vscode-jupyter-slideshow
2023-04-19 10:53:05.962 [error] Failed to install extension. ms-python.python
2023-04-19 10:53:05.963 [error] Error: end of central directory record signature not found,end of central directory record signature not found,end of central directory record signature not found,end of central directory record signature not found,end of central directory record signature not found,end of central directory record signature not found
    at c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:90:90057
    at Array.reduce (<anonymous>)
    at y (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:90:90043)
    at Y.D (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:90:81397)
    at async Y.z (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:90:78910)
    at async Y.installFromGallery (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:90:75312)
2023-04-19 10:53:05.963 [error] [uncaught exception in sharedProcess]: end of central directory record signature not found: CorruptZip: end of central directory record signature not found
    at yt.download (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:141)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async j.y (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:20893)
    at async j.h (c:\DEV\Applications\Microsoft VS Code\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:93:18962)

Keep getting the popup box in the bottom right saying "All installed extensions are temporarily disabled."
As well as .json files that will randomly refuse to validate even after running their contents through numerous online json fixers and validators all saying "valid!". I end up messing around with them for hours and hours until somehow something I do finally causes them to be OK again and I carefully close them while terrified on the edge of my seat.
<even less helpful, rant> This all started after a simple screenshot script I put together using Puppeteer that was working completely fine decided to not want to work anymore. It's been 3 days now of nonstop hair pulling, cursing, and sudden bursts of what I can only describe as exorcism. Cannot believe how defeating and pervasive this is being as time meanwhile ticks fast and slow closer and closer to a deadline days away that will basically render me homeless if I don't complete this project. On the bright side, all 140lbs of me could physically absolutely obliterate any human opponent on the planet right now. </AHHHHHHH!!!!>

I'm now getting a similar error as others in this thread:
2023-07-27 00:27:34.371 [error] Cannot read the extension from /c:/Users/EV-03/.vscode/extensions/esbenp.prettier-vscode-9.19.0: Error: Cannot read the extension from /c:/Users/EV-03/.vscode/extensions/esbenp.prettier-vscode-9.19.0

Possibly related: #187275
Possible related on Stack Overflow: Visual Studio Code issue with dowloading extensions

@starball5
The stack overflow question is related to the issue.
Vs Code Version: version 1.79
OS Version: Windows 11  21H2  22000.2176
Updating vscode, installing extensions or, updating extensions lead to an error:  Error while updating 'Astro' extension. Please check the [log](command:workbench.action.showWindowLog) for more details.  It's not limited to a specific extension.
Any attempt to update vscode generates this error net::ERR_INVALID_ARGUMENT
Output window contains
2023-08-05 12:19:26.268 [error] Error: net::ERR_INVALID_ARGUMENT
    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:49312)
    at SimpleURLLoaderWrapper.emit (node:events:513:28)
2023-08-05 12:19:26.296 [error] net::ERR_INVALID_ARGUMENT: Error: net::ERR_INVALID_ARGUMENT
    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:49312)
    at SimpleURLLoaderWrapper.emit (node:events:513:28)

@isidorn @sandy081 FYI, i keep getting the error, if that can help i let information about my errors
I just install the version 1.79.2 - this is the lastest version i can download with company rules :
Version: 1.79.2 (system setup)
Commit: 695af097c7bd098fbf017ce3ac85e09bbc5dda06
Date: 2023-06-14T08:57:04.379Z
Electron: 22.5.7
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044
Error still appear when i try to install any extensions even with "extensions.verifySignature": false in my settings.json :
2023-10-02 00:00:43.861 [info] Getting Manifest... eamodio.gitlens
2023-10-02 00:00:43.863 [info] Getting Manifest... financialforce.lana
2023-10-02 00:00:43.864 [info] Getting Manifest... rangav.vscode-thunder-client
2023-10-02 00:00:43.880 [error] Failed to install extension. eamodio.gitlens
2023-10-02 00:00:43.880 [error] Error: net::ERR_INVALID_ARGUMENT
at SimpleURLLoaderWrapper. (node:electron/js2c/browser_init:2:49312)
at SimpleURLLoaderWrapper.emit (node:events:513:28)
2023-10-02 00:00:43.881 [error] Failed to install extension. financialforce.lana
2023-10-02 00:00:43.881 [error] Error: net::ERR_INVALID_ARGUMENT
at SimpleURLLoaderWrapper. (node:electron/js2c/browser_init:2:49312)
at SimpleURLLoaderWrapper.emit (node:events:513:28)
2023-10-02 00:00:43.882 [error] Failed to install extension. rangav.vscode-thunder-client
2023-10-02 00:00:43.882 [error] Error: net::ERR_INVALID_ARGUMENT
at SimpleURLLoaderWrapper. (node:electron/js2c/browser_init:2:49312)
at SimpleURLLoaderWrapper.emit (node:events:513:28)
2023-10-02 00:07:08.464 [info] Getting Manifest... financialforce.lana
2023-10-02 00:07:08.470 [error] Failed to install extension. financialforce.lana
2023-10-02 00:07:08.470 [error] Error: net::ERR_INVALID_ARGUMENT
at SimpleURLLoaderWrapper. (node:electron/js2c/browser_init:2:49312)
at SimpleURLLoaderWrapper.emit (node:events:513:28)
2023-10-02 00:07:16.773 [info] Getting Manifest... rangav.vscode-thunder-client
2023-10-02 00:07:16.780 [error] Failed to install extension. rangav.vscode-thunder-client
2023-10-02 00:07:16.780 [error] Error: net::ERR_INVALID_ARGUMENT
at SimpleURLLoaderWrapper. (node:electron/js2c/browser_init:2:49312)
at SimpleURLLoaderWrapper.emit (node:events:513:28)
2023-10-02 00:07:36.929 [info] Getting Manifest... salesforce.sfdx-code-analyzer-vscode
2023-10-02 00:07:36.933 [error] Failed to install extension. salesforce.sfdx-code-analyzer-vscode
2023-10-02 00:07:36.933 [error] Error: net::ERR_INVALID_ARGUMENT
at SimpleURLLoaderWrapper. (node:electron/js2c/browser_init:2:49312)
at SimpleURLLoaderWrapper.emit (node:events:513:28)

I same have this on my Ubuntu and "extensions.verifySignature": false wont fix it

Well, I've retired from my job and this still appears to be an issue.  Good luck to everyone getting this error. :)

I just get rid of proxy with auth. Not perfect decision, but it's better to turn on/off each update

Can you (those who subscribed) please verify if this issue still exists?

Remove the setting extensions.verifySignature if you have set it (in user and remote settings)
Restart VS Code
Set Log Level to Trace - F1 > Developer: Set Log Level > Trace
Install an extension
Share the output - F1 > Show View... > Shared, if you are using remote, then share F1 > Show View... > Server

This issue is still happening for me @sandy081
2024-04-01 10:40:41.246 [trace] [code cache cleanup]: Starting to clean up old code cache folders.
2024-04-01 10:40:41.247 [trace] [storage cleanup]: Starting to clean up workspace storage folders for unused empty workspaces.
2024-04-01 10:40:51.243 [trace] [language pack cache cleanup]: Starting to clean up unused language packs.
2024-04-01 10:40:52.985 [info] Getting Manifest... github.copilot
2024-04-01 10:40:52.992 [error] Failed to install extension. github.copilot
2024-04-01 10:40:52.992 [error] Error: net::ERR_INVALID_ARGUMENT
    at SimpleURLLoaderWrapper.<anonymous> (node:electron/js2c/browser_init:2:110219)
    at SimpleURLLoaderWrapper.emit (node:events:514:28)

Version: 1.87.2 (Universal)
Commit: 863d2581ecda6849923a2118d93a088b0745d9d6
Date: 2024-03-08T15:21:31.043Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 23.4.0

I had a strange value in my settings.json for "http.proxyAuthorization". See https://github.com/microsoft/vscode/issues/176609#issuecomment-1477211460.

Closing this as there is no reports/feedback being provided for the comment


How to reuse a saved card

Hi,
I'm migrating from legacy Payum/Stripe in order to comply to new SCA regulations.
This is working beautifully with simple one-time payments, still I can't figure out how to charge a saved card.
Previously I just had to retrieve the "customer" token, I had stored on my db, and capture would charge the corresponding card. It looks like this library does not support this flow at all, yet.
I'm studyng Stripe docs and this is the point I reached:

after a successful one-tipe payment with Checkout Session a PaymentIntent object is retrieved.

then

I should use customer token to retrieve his/her PaymentMethod and get pm_***** token.
then I should create a new PaymentIntent passing customer and payment_method tokens, with the new amount to charge, and confirm it.

In Postman, this does work.
Now I'm bashing my head on Payum docs and examples in order to understand how to achieve this. Any plan to implement this in this library?
EDIT: I've already set up my custom GatewayFactory which extends StripeCheckoutSessionGatewayFactory and started creating custom Actions.

Hello @francesco-laricchia
The gateway stripe_checkout_session allow to pay, subscribe or store a credit card thanks to a Stripe hosted portal, then at the end of the process returning to your website the payment/subscription/setup is completed. But nothing disallow you to use each API Action outside those Stripe Checkout processes to make your own re-payment flow.
There is now (master branch) a CreatePaymentIntent request which will allow you to create your own PaymentIntent, here is an exemple :
$model = [
    'amount' => 2000,
    'currency' => 'eur',
    'payment_method' => 'pi_123456',
    'customer' => 'cu_123456',
];
$request = new CreatePaymentIntent($model);
$payum->getGateway('stripe_checkout_session')->execute($request);

$paymentIntent = $request->getApiResource();

Let me know if you succeeded.

Let me know if you succeeded.

I eventually managed to complete a payment with a previously saved card, even if it requires to go through SCA flow again every time. Thank you for the hint!
With legacy Payum/Stripe I used GetCreditCardTokenAction to save card token, which was only the "customer" field, to my database so I could Stripe::charge() the same card later without asking the user for the card data again.
I'm still using it with your library, but now after the first payment succeeds I set
$token = [
    'customer' => $model['customer'],
    'payment_method' => $model['payment_method'],
];

$request->token = serialize($token);

In CaptureAction, I'm just adding
$model->offsetSet('return_url', $token->getTargetUrl());

in order to manage SCA authentication request. And this is all I need to create a new PaymentIntent. If no SCA is required again, that's it. If SCA il enforced, I created a new action so:
$redirectToScaPage = new RedirectToScaPage($paymentIntent->toArray());
$this->gateway->execute($redirectToScaPage);

redirects the user's browser to Stripe hosted authorization page which will manage it all for me. Then it goes back to return_url, the payment is captured and the order fulfilled.
Payum is not the easiest stuff to learn, but I'm getting to the grips with it.

@francesco-laricchia using Stripe JS Element through stripe_js gateway is also possible I made a test project with your workflow and this work also well with or without SCA.
Here is the payment object I set (prepare.php if we follow the original Payum doc):
use Payum\Core\Model\Payment;

$storage = $payum->getStorage(Payment::class);

/** @var Payment $payment */
$payment = $storage->create();
$payment->setNumber(uniqid());
$payment->setCurrencyCode('EUR');
$payment->setTotalAmount(123);
$payment->setDescription('A description');
$payment->setClientId('anId');
$payment->setClientEmail('foo@example.com');
$payment->setDetails([
    'customer' => 'cus_123456',
    'payment_method' => 'card_123456'
]);

$storage->update($payment);

Here is the twig overrides I build to handle your case :
{# templates/bundles/FluxSEPayumStripe/Action/pay.html.twig #}
{% extends "@!FluxSEPayumStripe/Action/pay.html.twig" %}

{% block payum_body %}
    {{ parent() }}
<form action="{{ action_url|default('') }}" method="POST" name="payment-form" id="payment-form" data-secret="{{ model.client_secret }}">

</form>
{% endblock %}

{% block payum_javascripts_stripejs_common %}

{% endblock %}

The SCA popup will be prompt if needed then the customer is redirected to the end of the Payum process.
So you have choices between using stripe checkout session portal or a pure Stripe JS implementation ;)


Interfaces defined in WIG does not use correct JavaScript name

WIG compiler generates an Inline attribute which is then ignored by the Reflector creating the WS metadata for the assembly. Should generate Name attribute instead, which also allows proper inheriting by user-defined classes.

Previously, compiling calls against WIG-defined interface methods was wrong, used the .NET name instead of any inlines set in WIG definition.
This change has both an upside and a downside:

WIG-defined interfaces are using only the Name attribute, so no custom inlines defined on them will have an effect (WIG API still allows it...).
They are now able to be implemented with your custom classes

The upside is the smaller, so this can be changed back partially so this is a non-breaking change:

WIG Interfaces with only methods defined on them with no custom inlines create interface metadata (using Name), allowing inheriting/implementing from your own WS-defined interfaces/classes.
all other WIG interfaces (having a JS property and/or custom inline) create class-like metadata (using Inlines). Trying to inherit/implement them in WS-code will fail, but they are perfect for defining mixins in WIG, and translation will use the inline correctly if you call the member through the interface.


updates to documentation and variable naming

remove offensive wording in variables where possible
sync documentation from subfolder into main folder

okay, auto merge was faster than i thought, i edited the rules and not reviews are mandatory


Convert this to a module

It'd probably be more portable and practical if this was converted into a Puppet module.

Sure! Nice proposal. I will add this to my todo list. If you are also interested in this, you are welcome to help :)

I am afraid I am swamped with other projects at the moment but it's very fast to do. You can use the puppet-module gem to create a template and then migrate your manifests into it.

Nice! Kudos.

thnx :)


fix(#201): normalize POSIX separators to support windows

Description
Fix #201 by normalizing the POSIX separators
Additional context
Also added some tests to vite-plugin-react-server-components-shim.ts. These validate not only the transformation, but also some of our import rules (no server components from client components).
Before submitting the PR, please make sure you do the following:

[x] Add your change under the Unreleased heading in the package's CHANGELOG.md
[x] Read the Contributing Guidelines
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123)
[x] Update docs in this repository for your change, if needed

@blittle Nice! Thanks so much for the tests as well!


fix(install): add the helm command to use leastPrivileged and PSP

Signed-off-by: Luca Guerra<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind user-interface

/kind content

/kind translation

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area videos

What this PR does / why we need it:
The GKE helm command did not include an option to configure Pod Security Policy. This feature has already been deprecated by Kubernetes and will be removed in version 1.25, but for now it is still needed in GKE, otherwise you will see messages like:
PodSecurityPolicy: unable to admit pod: [spec.securityContext.hostNetwork: Invalid value: true: Host network is not allowed to be used spec.volumes[0]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[1]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[2]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[3]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[4]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[5]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[6]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.volumes[7]: Invalid value: "hostPath": hostPath volumes are not allowed to be used spec.containers[0].securityContext.privileged: Invalid value: true: Privileged containers are not allowed]

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: LucaGuerra
To complete the pull request process, please assign jasondellaluce after the PR has been reviewed.
You can assign the PR to them by writing /assign @jasondellaluce in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @LucaGuerra! It looks like this is your first PR to falcosecurity/falco-website 🎉

My bad, that is not the default configuration but may only happen with old clusters with deprecated configurations.


Revisit card design

Charts list
Service Catalog services & plans list

This is the proposal we're going to implement :)


[FEATURE] snare and hi-hat plugins

Hi,
Maybe this is the wrong place to ask this, but it would be great to have plugins like ChowKick for snare and hi-hats. The quality of ChowKick is exceptional. If we could have for snares and hi-hat plugins, I'll not need my samples any more :-)

Hello!
A little bit of background:
The main synthesis engine for ChowKick was actually finished around July/August of 2020. At the time, my idea was to build a more complete "drum machine", with voices including kick, snare, hi-hat, cymbals, and maybe some toms, clap, cowbell, etc. Unfortunately, I had trouble finding the time to actually work on these other voices, so after 9 months of little-to-no progress, I decided to just finish ChowKick and release it on its own.
I would still love to build either a more complete drum machine, or more individual plugins for the different drum voices, but it will take some time to develop. At the moment, my schedule is pretty packed for next couple months, since I'm planning to release updates to a couple other plugins, and hopefully finish up another new one. After that (probably in the new year), I can try to make some time to work on more drum voices!
Thanks,
Jatin


Unpacking platform artifact issue

Describe issue
I could not success to unpack platrofm artifact. The same problem was with application artifact, and after few times, he  success to unpack application artifact. Between problem with unpacking, I also receive this message (few times) while I was trying to download artifacts.

Downloading C:\Temp\ba8562d5-92b7-4046-88cc-b858ae507029.zip
Retrying download...
Downloading C:\Temp\ba8562d5-92b7-4046-88cc-b858ae507029.zip
Download-File : Exception calling "DownloadFile" with "2" argument(s): "The operation has timed out."
At C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\<IP_ADDRESS>\Misc\Download-Artifacts.ps1:129 char:21

...             Download-File -sourceUrl $platformUrl -destinationFile $p ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Download-File], MethodInvocationException
FullyQualifiedErrorId : WebException,Download-File

Scripts used to create container and cause the issue

$artifactUrl = Get-BCArtifactUrl -version 16.2 -country is -select Latest -type OnPrem
$containerName = "IcelandCloud"
$auth = "Windows"
$licenseFile = "C:\BC16.flf"
New-NavContainer         -containerName $containerName
-accept_eula         -accept_outdated
-assignPremiumPlan         -auth $auth
-artifactUrl $artifactUrl         -includeAL
-isolation hyperv         -licenseFile $licenseFile
-restart no         -shortcuts Desktop
-updateHosts `
-alwaysPull

Full output of scripts

NavContainerHelper is version <IP_ADDRESS>
NavContainerHelper is running as administrator
Host is Microsoft Windows 10 Enterprise - 1909
Docker Client Version is 18.09.11
Docker Server Version is 18.09.11
Removing C:\ProgramData\NavContainerHelper\Extensions\IcelandCloud
Pulling image mcr.microsoft.com/dynamicsnav:10.0.18363.836-generic
10.0.18363.836-generic: Pulling from dynamicsnav
Digest: sha256:cbc86fccc7acc78d13075a5d64b70d60ec197f507eb833830c5bdf9e5362905a
Status: Image is up to date for mcr.microsoft.com/dynamicsnav:10.0.18363.836-generic
Using image mcr.microsoft.com/dynamicsnav:10.0.18363.836-generic
Downloading platform artifact /onprem/16.2.13509.13779/platform
Downloading C:\Temp\71a190ed-7b2f-4df2-b78c-b3776c082bed.zip
Unpacking platform artifact
Remove-Item : Cannot find path 'C:\bcartifacts.cache\onprem\16.2.13509.13779\platform-tmp\Applications\APIV1\Source' because it does not exist.

Did I doing something wrong?

I don't have a timeout on the download and it looks like the download on your machine is taking longer than the standard timeout causing this issue.
I will fix this in the next NavContainerHelper (probably shipped tomorrow morning).


builder.Services.TryAddTransient<IEventService, DefaultEventService>() repeats twice

 builder.Services.TryAddTransient<IEventService, DefaultEventService>(); repeats twice in
 public static IIdentityServerBuilder AddPluggableServices(this IIdentityServerBuilder builder) method of https://github.com/IdentityServer/IdentityServer4/blob/dev/src/IdentityServer4/Configuration/DependencyInjection/BuilderExtensions/Core.cs
It have technical reason?

thanks for reporting. fxed.


feat: Allow annotations in Meltano project files

Closes #7092

@meltano/engineering This PR currently implements support for annotations essentially anywhere within Meltano project files. It works, but as discussed in the codesharing call on 2022-12-15, it's a mess, and we aren't aware of any straightforward ways of improving it that would be worth the time commitment. Additionally, it's unclear how the Manifest should handle them when it hoists stuff from an environment up to the top level.
Thoughts on reducing the scope down to permitting an annotations field at the top-level of meltano.yml only, rather than allowing annotations anywhere? Later on it'll be easy enough to add support for annotations elsewhere (i.e. by doing what this PR currently does), but removing support for it somewhere is a breaking change, so I'm inclined to only permit them everywhere now if we have a good way to implement that.

Superseded by:

#7115


CLOUDP-218697: Fix get latest tag

The bash function get_latest_tag was failing in some cases, detecting older tags as the latest.
This fix changes the way the latest tag is computed so we always get correct results.
✅ Release charts dryrun detects NO skews between latest released chart and latest tag
All Submissions:

[X] Have you signed our CLA?

See for example:
https://github.com/mongodb/helm-charts/actions/runs/7394981709/job/20117479890
released result: "mongodb/mongodb-atlas-operator     	2.0.1        	2.0.1      	MongoDB Atlas Operator - a Helm chart for insta..."
Looking for versions...
version from tag: 1.9.2
version from chart: 2.0.1
...
released result: "mongodb/community-operator     	0.9.0        	0.9.0      	MongoDB Kubernetes Community Operator       "
Looking for versions...
version from tag: 0.8.3
version from chart: 0.9.0

This provoked errors as it tried to re-release versions already released.


Update to Manifest V3

Chrome will deprecate and remove Extension Manifest V2 in January 2023

Migration guide: https://developer.chrome.com/docs/extensions/mv3/intro/mv3-migration/
API overview: https://developer.chrome.com/docs/extensions/mv3/intro/mv3-overview/

Notably, Manifest V3 extensions can't inject JavaScript as strings, which Clozoom relies on currently.

Moved to V3!


Configuration files should be placed under a single directory

Hi Jim,
First of all, thanks for this great utility. I'd like to report the following minor issue.
I've used the installer for a system-wide installation and also the portable version and I've noticed that the following are created:

the C:\User\USERNAME\Documents\SuperPutty directory is always created, although a different directory has been set in the initial configuration dialog.
the configuration file C:\Users\USERNAME\SuperPuTTY.settings

Plus the extra directory that is set in the configuration dialog, which contains the layouts.
It would be nice if you just added all the configuration files under C:\Users\USERNAME\AppData\Roaming\SuperPuTTY\, which is the expected directory for the application's configuration files.
If the various Windows versions do not use a consistent path for software configurations, I could help you by doing some research about it and report back with my findings.
Thanks in advance,
George

Thanks for the report George. This is a legacy issue from back in the XP days I believe. It can be changed, but some logic will have to be put in place to migrate the old configuration files. Not only for the settings file but also the Layout files. I'll see what I can do when this becomes low hanging fruit.

Hi Jim,
Thanks for your quick reply. This is indeed a very low priority issue. I submitted this report while revising my backup strategy and attempting to gather as many configuration files / key files as possible under appdata\roaming\ (...there is a long way until this point is reached). I don't really expect any change soon.
Thanks for taking it into consideration for the future and, again, thanks for this great software!
George


[topgen,Makefile] Remove code generated by topgen

The clkmgr, pin_mux, and rstmgr have their reg_top and reg_pkg generated by topgen, so the corresponding files in their hw/ip directory are unnecessary.
There is no use to have hw/Makefile handle these IPS either.

This is problematic unless modules are ipgen, so it is not worth doing now. Closing this.


emacs: darwin: use architecture-native SDK

Description of changes

#253892 bumped the Emacs derivations to apple_sdk_11_0 for headers required by the Mac port on Apple Silicon Macs. That change caused many issues on older macOS versions. This change switches back to the platform-native SDK (10.12 on x86_64-darwin and 11.0 on aarch64-darwin) and gates the newly required headers by architecture.
CC @quentinmit and @knl. I tested emacs-macport for x86_64-darwin and the problematic aligned_alloc isn't being imported anymore, but I would appreciate confirmation from your end.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

??