Linux: An OS keyring couldn't be identified for storing the encryption related data in your current desktop environment

Does this issue occur when all extensions are disabled?: Yes
I referred to https://code.visualstudio.com/docs/editor/settings-sync#_troubleshooting-keychain-issues
This is the error part of my log after running code-insiders --verbose --vmodule="*/components/os_crypt/*=1":
[314774:0707/210405.156953:INFO:CONSOLE(627)] "%cTRACE color: #888 [mainThreadSecretState] Setting password for vscode.github-authentication extension:  github.auth", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210405.157113:INFO:CONSOLE(627)] "%cTRACE color: #888 [NativeSecretStorageService] Notifying user that secrets are not being stored on disk.", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210405.158116:INFO:CONSOLE(627)] "%cTRACE color: #888 DialogService#prompt An OS keyring couldn't be identified for storing the encryption related data in your current desktop environment.", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[314774:0707/210409.420345:INFO:CONSOLE(627)] "%cTRACE color: #888 [secrets] encrypting secret for key: {"extensionId":"vscode.github-authentication","key":"github.auth"}", source: vscode-file://vscode-app/opt/visual-studio-code-insiders/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[main 2023-07-08T02:04:09.420Z] [EncryptionMainService] Encrypting value.
[main 2023-07-08T02:04:09.422Z] Error: Error while encrypting the text provided to safeStorage.encryptString. Encryption is not available.
    at e.$U2b.encrypt (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:42:11004)
    at Object.call (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:25:4844)
    at R.s (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:23:5128)
    at R.q (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:23:4644)
    at o.value (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:23:4051)
    at y.w (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:1906)
    at y.x (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:1976)
    at y.fire (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:2192)
    at o.value (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:16:38681)
    at y.w (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:1906)
    at y.fire (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:2123)
    at o.value (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:16:38875)
    at y.w (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:1906)
    at y.fire (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:18:2123)
    at se (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:16:41018)
    at IpcMainImpl.f (/opt/visual-studio-code-insiders/resources/app/out/vs/code/electron-main/main.js:19:96358)
    at IpcMainImpl.emit (node:events:513:28)
    at EventEmitter.<anonymous> (node:electron/js2c/browser_init:2:80979)
    at EventEmitter.emit (node:events:513:28)
[314774:0707/210409.425211:INFO:CONSOLE(627)] "%c  ERR color: #f33 Error: Error while encrypting the text provided to safeStorage.encryptString.   Must be the update to 1.80.
Manually configuring the keyring to use results in this:
code-insiders --password-store="gnome"
Warning: 'password-store' is not in the list of known options, but still passed to Electron/Chromium.

It seems to work.
I figured this is a bug since I had gnome-keyring installed, it wasn't being used, and I had to manually configure it.

I tried to setup the runtime args according to the support article I listed:

Can you please include the very top of the logs? The part that contains the stuff call out here:
https://code.visualstudio.com/docs/editor/settings-sync#_linux
Or even the whole log works.

Additionally, what desktop environment & window manager are you using?

For me this is happening on i3 on arch, also using gnome keyring.
[64727:0708/211450.886024:VERBOSE1:key_storage_util_linux.cc(54)] Password storage detected desktop environment: (unknown)
[64727:0708/211450.886034:VERBOSE1:key_storage_linux.cc(122)] Selected backend for OSCrypt: BASIC_TEXT
[64727:0708/211450.886044:VERBOSE1:key_storage_linux.cc(142)] OSCrypt did not initialize a backend.

Additionally, what desktop environment & window manager are you using?

Uh.. sorry I'll try to find the log file if they are kept.  Also I'm using a similar setup as GerritPlehn, i3 on Arch.

Here is the main.log if that's the one you need.

Related: https://github.com/microsoft/vscode/issues/186792
Chromium failing to detect i3 seems to be the common thread

Getting the same error as well on bspwm.

Same issue on Sway and my gnome-keyring-daemon is correctly set-up.
Launching code with code --password-store="gnome" as suggested here works.

Same issue here, using Ubuntu 23.04 with i3wm.

Same for me. i3wm on Manjaro 23.0.0

Same for me, using EndeavourOS 6.4.1-arch2-1 and qtile.

Same issue with an i5, and "password-store": "gnome" fixes it.
Version: 1.80.0
Commit: 660393deaaa6d1996740ff4880f1bad43768c814
Date: 2023-07-04T13:39:48.236Z
Electron: 22.3.14
ElectronBuildId: 21893604
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.15.108-18910-gab0e1cb584e1
Also getting this, even though it seems to be working: Property password-store is not allowed. in argv.json

I'm seeing this issue as well on Arch running XMonad.

Same happening on Arch with awesomewm. Adding "password-store": "gnome" to ~/.vscode/argv.json fixed the issue.

Same happening on Ubuntu 22.04 with i3wm.  Adding "password-store": "gnome" to ~/.vscode/argv.json fixed the issue.

Same on Lubuntu 23.04 (LXQt) and adding "password-store": "gnome" to ~/.vscode/argv.json also resolves.

From #187436.
I'm using archlinux with hyprland as desktop environment.
To manage my keyring I have installed kwallet.
The pop-up disappear when I set password-store to kwallet5.

Additionally I've configured dbus to start the service automatically by creating the file /usr/share/dbus-1/services/org.freedesktop.secrets.service with the content:
[D-BUS Service]
Name=org.freedesktop.secrets
Exec=/usr/bin/kwalletd5

I don't know if it's possible for vscode to use the service configured in org.freedesktop.secrets as keyring manager :thinking:

Additionally, what desktop environment & window manager are you using?

Got the same error in Xfce4

Got the same error in Xfce4. Using gnome-keyring
Adding "password-store": "gnome"
to ~/.vscode/argv.json solved it.
I am using:
❯ neofetch --stdout
zaid@archlinux
--------------
OS: Arch Linux x86_64
Host: 20DSS02V00 ThinkPad L450
Kernel: 6.1.38-1-lts
Uptime: 7 mins
Packages: 534 (pacman)
Shell: bash 5.1.16
Resolution: 1366x768
DE: Xfce 4.18
WM: Xfwm4
WM Theme: Default
Theme: Adwaita-dark [GTK2/3]
Icons: elementary [GTK2], Adwaita [GTK3]
Terminal: alacritty
CPU: Intel i3-5005U (4) @ 2.000GHz
GPU: Intel HD Graphics 5500
Memory: 1813MiB / 7832MiB

❯ gnome-keyring version
gnome-keyring: 42.1

It seems that last VsCode update broke everything for everyone not using a "standard" Linux distribution.
Same issue with Manjaro/i3 here, and the flag fixed it for me but is not satisfying

Fedora/i3wm, same issue.

Same issue on Debian 11 (ChromeOS)/aarch64 with version 1.80

Ubuntu/xmonad, experiencing the same issue. password-store workaround works, but I'd like a more fundamental fix.

Same happening on Arch with awesomewm. Adding "password-store": "gnome" to ~/.vscode/argv.json fixed the issue.

Same issue in Arch Linux with i3wm. Adding password-store also fixed it.

Not sure if there is a use piling on at this point but same issue ArchLinux with qtile.

Also happens on Chromebook. The password-store workaround did the trick.

Adding "password-store": "gnome" to my argv.json solved this issue on arch linux (kernel 6.4.3-arch1-2.1) with hyprland. Thank you very much for pointing this out!

Adding "password-store": "gnome" to ~/.vscode/argv.json worked for me on Fedora 37 with i3wm.

Unsurprisingly, same with dwm on Debian trixie.

Mine is keepassxc , which can be fixed with "gnome-libsecret" . I am also an arch user, yay vscodium-bin-features can log in with a Microsoft account, just mention it.
Maybe this option name is a bit misleading.

I use https://github.com/yousefvand/secret-service and for the longest time it did work fine, until whatever update broke everything. It still registers as a org.freedesktop.secrets compatible specification, yet still will not work. Pls fix guys

This issue is also present on code/stable,now 1.80.1-1689183569 on Kali Linux with i3 4.22 (2023-01-02).
As others mentioned, "password-store": "gnome" fixes this issue temporarily.

Issue present on code 1.80.1 on Fedora 38 with i3 version 4.22 (2023-01-02); fixed temporarily with the "password-store": "gnome" tweak.

Came here, to say thank you for the workaround, facing the same issue on Arch + Sway.

Same issue with sway on Arch Linux. According to this doc it seems we indeed need to setup the keyring.
What I did:

install gnome-keyring (since it wasn't installed by default with sway)
add either  "password-store"="gnome" in .vsode/argv.json or --password-store=gnome in .config/code-flags.conf
launch VSCode and setup a password for gnome-keyring

Quite annoying to have to install gnome-keyring (or whatever supported keyring).

Can confirm that manually adding "password-store": "gnome" to the argv.json file worked.
Had to add the arg manually after running code with code --password-store="gnome" failed to work.

@TylerLeonhardt @deepak1556 can you provide an update on this issue?

Any workaround for code-server? code-server 1.81.0 on Fedora 38 is still not working.

vscode 1.81.0 is not working with this workaround.
[210343:0807/152610.540842:INFO:CONSOLE(762)] "You're running in a GNOME environment but the OS keyring is not available for encryption. Ensure you have gnome-keyring or another libsecret compatible imp
lementation installed and running.", source: vscode-file://vscode-app/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (762)
[210343:0807/152610.541209:INFO:CONSOLE(627)] "%cTRACE color: #888 [secrets] encrypting secret for key: {"extensionId":"vscode.github-authentication","key":"github.auth"}", source: vscode-file://vscode-
app/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[main 2023-08-07T07:26:10.541Z] [EncryptionMainService] Encrypting value.
[main 2023-08-07T07:26:10.541Z] Error: Error while encrypting the text provided to safeStorage.encryptString. Encryption is not available.
    at R.encrypt (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:42:10994)
    at Object.call (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:25:4844)
    at P.s (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:23:5128)
    at P.q (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:23:4644)
    at o.value (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:23:4051)
    at b.w (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:1906)
    at b.x (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:1976)
    at b.fire (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:2192)
    at o.value (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:16:38681)
    at b.w (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:1906)
    at b.fire (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:2123)
    at o.value (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:16:38875)
    at b.w (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:1906)
    at b.fire (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:2123)
    at se (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:16:41018)
    at IpcMainImpl.f (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:19:96331)
    at IpcMainImpl.emit (node:events:513:28)
    at EventEmitter.<anonymous> (node:electron/js2c/browser_init:2:80979)
    at EventEmitter.emit (node:events:513:28)

I am using NixOS + i3wm, and the gnome-keyring service is enabled.

Same issue with sway on Arch Linux. According to this doc it seems we indeed need to setup the keyring. What I did:
* install `gnome-keyring` (since it wasn't installed by default with sway)
* add either  `"password-store"="gnome"` in `.vsode/argv.json` or `--password-store=gnome` in `.config/code-flags.conf`
* launch VSCode and setup a password for gnome-keyring

Quite annoying to have to install gnome-keyring (or whatever supported keyring).

Similar setup, but I don't use gnome-keyring - instead use another libsecret backend.
According to electron docs you can also pass other options, such as --password-store=gnome-libsecret - and this worked for me - without having to install gnome-keyring.

I am using NixOS with gnome 44 and gnome-keyring, I recently updated to VSCode 1.81 and I am running into the same issue, previously mentioned fixes dont work in 1.81, I have tried with --password-store=gnome,--password-store=gnome-libsecret and even --password-store=gnome-keyring but none of them works, for now my only option is to use ``--password-store=basic` because it is the only option that preserves my login.
I am getting this same error

vscode 1.81.0 is not working with this workaround.
[210343:0807/152610.540842:INFO:CONSOLE(762)] "You're running in a GNOME environment but the OS keyring is not available for encryption. Ensure you have gnome-keyring or another libsecret compatible imp
lementation installed and running.", source: vscode-file://vscode-app/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (762)
[210343:0807/152610.541209:INFO:CONSOLE(627)] "%cTRACE color: #888 [secrets] encrypting secret for key: {"extensionId":"vscode.github-authentication","key":"github.auth"}", source: vscode-file://vscode-
app/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/workbench/workbench.desktop.main.js (627)
[main 2023-08-07T07:26:10.541Z] [EncryptionMainService] Encrypting value.
[main 2023-08-07T07:26:10.541Z] Error: Error while encrypting the text provided to safeStorage.encryptString. Encryption is not available.
    at R.encrypt (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:42:10994)
    at Object.call (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:25:4844)
    at P.s (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:23:5128)
    at P.q (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:23:4644)
    at o.value (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:23:4051)
    at b.w (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:1906)
    at b.x (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:1976)
    at b.fire (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:2192)
    at o.value (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:16:38681)
    at b.w (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:1906)
    at b.fire (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:2123)
    at o.value (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:16:38875)
    at b.w (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:1906)
    at b.fire (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:18:2123)
    at se (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:16:41018)
    at IpcMainImpl.f (/nix/store/9x3bq8mmzg15js30sm581y2am4idjbj6-vscode-1.81.0/lib/vscode/resources/app/out/vs/code/electron-main/main.js:19:96331)
    at IpcMainImpl.emit (node:events:513:28)
    at EventEmitter.<anonymous> (node:electron/js2c/browser_init:2:80979)
    at EventEmitter.emit (node:events:513:28)

I am using NixOS + i3wm, and the gnome-keyring service is enabled.

@BlankParticle your situation appears to be different because VS Code detected GNOME. Can you please open a new issue and follow our troubleshooting? https://code.visualstudio.com/docs/editor/settings-sync#_troubleshooting-keychain-issues

I tried the troubleshooting guide, but nothing fixes this. I think it is an issue coming down from electron

Same on Sway WM. Launching with $ code --password-store="gnome" does not work, but adding "password-store":"gnome" to argv.json works.

mann why do none of those work for me.. what pkg do you have for vs code on arch guys?

mann why do none of those work for me.. what pkg do you have for vs code on arch guys? I use code code-features and code-marketplace

I am using visual-studio-code-bin 1.81.0-1 from AUR and setting:
	"password-store": "gnome"

in argv.json works. Of course, for this to work, you need to install and setup gnome-keyring-daemon.

Of course, for this to work, you need to install and setup gnome-keyring-daemon. The guide I used.

Alright I will check this out thanks ! I didnt instal gnome-keyring manually since it was a dependency of code-features on AUR

Why does VSCode even attempt to initialize the keyring integration when one doesn't attempt to use the settings sync feature?

Why does VSCode even attempt to initialize the keyring integration when one doesn't attempt to use the settings sync feature?

It is not only used for the settings sync feature. It also handle secrets (such as auth against Github for example)

For those with NixOS, I spotted that there's now a fix in master while investigating this (Thanks @BlankParticle):
https://github.com/NixOS/nixpkgs/commit/ed2f5f18292f238762fde3a2076ee727c029e917
(Also, hint for others can be to check your LD_LIBRARY_PATH, turned out mine was messed up so I had to fix that too)

check your LD_LIBRARY_PATH, turned out mine was messed up so I had to fix that too

How exactly did you fix that and how is it messed up? mine is just empty

check your LD_LIBRARY_PATH, turned out mine was messed up so I had to fix that too

How exactly did you fix that and how is it messed up? mine is just empty

I had a module that was badly written;
  environment.sessionVariables.LD_LIBRARY_PATH = lib.mkIf config.gpu.nvidia.enableVulkan "${pkgs.vulkan-loader}/lib:${pkgs.wayland}/lib:$LD_LIBRARY_PATH";

Which ended up being LD_LIBRARY_PATH='/some-correct-paths:$LD_LIBRARY_PATH' (literally $LD_LIBRARY_PATH as path instead of expanded, so a bunch of library paths was missing instead of being appended, including libsecret). I just removed it since I don't need it (restart required)
I noticed it was incorrect when I manually wanted to start VSCode with libsecret my known existing path (LD_LIBRARY_PATH=/nix/store/2iann9zk6bkm3cdi7vx4wa3hmc49zfmx-libsecret-0.20.5/lib code-insiders)

Oh yeah, some other stuff I investigated while troubleshooting (maybe useful info for some):

I also tried adding the deprecated libgnome-keyring, but that was a dead end (producing OSCrypt tried Libsecret but couldn't initialise.), so probably no point in trying that

I ensured my gnome-keyring-daemon was started with secrets (the --components=pkcs11,secrets,ssh argument). That wasn't the issue since that was already my case, but might worth checking.
# If using nixos home-manager
services.gnome-keyring.components = ["pkcs11" "secrets" "ssh"];

Same on Sway WM. Launching with $ code --password-store="gnome" does not work, but adding "password-store":"gnome" to argv.json works.

For me it's the exact opposite:  $ code --password-store="gnome" works, but adding "password-store":"gnome" to argv.json has no effect.
I am using i3wm under Debian 12 with code 1.81.1. Gnome Keyring is set up, unlocked, and works both in terminal and if using the --pasword-store="gnome" argument when starting gnome.

Maybe related https://www.reddit.com/r/archlinux/comments/15sse7i/psa_chromium_dropped_gnomekeyring_support_use/?utm_source=share&utm_medium=ios_app&utm_name=ioscss&utm_content=1&utm_term=1 ?

Turns out, for VS code to detect the keyring properly, I need two things:

password-store must be set to gnome or gnome-libsecret
the environment variable SSH_AUTH_SOCK must be set to /run/user/1000/keyring/ssh

Since the latter isn't possible in the argv.json file, it explains why it didn't work properly for me.
Conclusion: VS code is not detecting the SSH auth socket properly under i3.

I'm using sway on Arch, but the solutions above somehow didn't work for me. So, I tried to set XDG_CURRENT_DESKTOP to 'GNOME', and it worked. I don't know whether this is a good solution or not.

I'm not sure if this issue is even fixable then without adding custom logic to properly detect available password stores, the way electron does it isnt very good

I had This Issue for a while on the Linux Mint . This worked: you can make the flag permanent by editing the code-flags.conf file in your .config directory. To do this, open your terminal type nano ~/.config/code-flags.conf, and press enter. This will open the file in a text editor. In the file, add a new line with the flag --password-store=“gnome” and save the file by pressing Ctrl+O and then Ctrl+X.

That didn't work for me, as well as many people in this thread, if the solution was that simple, I wouldn't have gone through the trouble of trying 20 previous versions until I found a working one.

As a follow up update, I started to use https://github.com/nullobsi/pass-secrets which is a org.freedesktop.secrets compatible implementation using pass as its backend, which is powered by gpg keys. Needless to say, VSCode will still not work. I'm not sure what's changed between its attempts to use SecretService, but it needs to be changed because these things worked before and don't anymore.

Here are the detailed steps that I used to fix this on my raspberry pi:

Open a new terminal in Linux
Use command: nano ~/.vscode/argv.json to edit VSCode's settings
Scroll to the end of the file and add "password-store": "gnome" on a new line, before the closing curly bracket. Be sure to add a comma to the previous line (as shown by the arrow in the screenshot below)

Use CTRL + X to exit the file and confirm the prompts to update and save your changes
Open VSCode as normal

If it is still not working, check your VSCode logs by opening the latest main.log file in home/pi/.config/Code/logs/

If you see an error like the one below then you have made a mistake with the syntax when editing VSCode's settings. In my case, I had missed out a comma but you could also have missed out a quotation mark.

Hope this helps someone :)

I closed the window and apparently that took the same action as clicking "Use weaker encryption". I'm not sure where it stored that setting. Anyone has an idea how to revert that? (I would like that the popup keeps showing if this breaks again)

I closed the window and apparently that took the same action as clicking "Use weaker encryption" (popup doesn't show anymore). I'm not sure where it stored that setting. Anyone has an idea how to revert that? (I would like that the popup keeps showing if this breaks again)

@Ten0
press Ctrl + Shift + P  --> search configure runtime argument --> then you will see the file

@pavanbhat1999
Thanks. However I didn't see any extra line in there following the closing of that window. Are you sure this is where configuring to insecure from the pop-up writes?

Having the same issue with keepassXC secret service integration turned on. I just curious when do you planing to fixing this issue it sucks to be on 1.79.2 version tbh

same issue: "Property password-store is not allowed."
keyring: gnome
wm: Awesomewm
OS: Archlinux

Anyone able to make it work on NixOS?

Does this work on .vscode-oss ? I think the arch linux package of vscode is the oss version, so I edit .vscode-oss/argv.json with "password-store": "gnome" and still no luck.

Ask 10 Persons, and you get 15 anseres...here we go:
export DESKTOP_SESSION=xfce
code

on i3 will also do the job.

"password-store": "gnome"

Worked fine on hyprland

On VS Code 1.83.1 under Mint 21.2 (Victoria), when I try to set "password-store": "basic" in argv.json, VS Code says "Property password-store is not allowed".

On VS Code 1.83.1 under Mint 21.2 (Victoria), when I try to set "password-store": "basic" in argv.json, VS Code says "Property password-store is not allowed".

Same, it seems still to work?

Does anyone have this problem on Windows?
First time seeing this on Windows 10 Pro

I get this issue on Mac when logging into Github - either the Github Actions or Copilot extensions - has anyone run into this on Mac?

@sashap8 can you open a separate issue? It's probably not related to Linux.
When you open it, please follow the troubleshooting steps to make sure that you include the necessary information.

@sashap8 can you open a separate issue? It's probably not related to Linux.
When you open it, please follow the troubleshooting steps to make sure that you include the necessary information.

Thanks @TylerLeonhardt, I submitted an issue with system details and reproduction steps. I looked through common troubleshooting cases, but didn't find any that seemed relevant. Feel free to let me know if there's any more context I should be providing though! Thanks again.

Solution if you're using an non-popular window manager

install gnome-keyring libsecret. On arch you can run sudo pacman -S gnome-keyring libsecret
open vscode by terminal code --password-store="gnome"
If this solution works for you, you can persist the value of password-store by opening the Command Palette (Ctrl+Shift+P) and running the Preferences: Configure Runtime Arguments command. This will open the argv.json file where you can add the setting "password-store":"gnome" (this step is from https://code.visualstudio.com/docs/editor/settings-sync#_troubleshooting-keychain-issues).

Solution if you're using a non-popular window manager
1. install `gnome-keyring libsecret`. On arch you can run `sudo pacman -S gnome-keyring libsecret`

2. open vscode by terminal `code --password-store="gnome"`

3. If this solution works for you, you can persist the value of password-store by opening the Command Palette (Ctrl+Shift+P) and running the Preferences: Configure Runtime Arguments command. This will open the argv.json file where you can add the setting "password-store":"gnome" (this step is from https://code.visualstudio.com/docs/editor/settings-sync#_troubleshooting-keychain-issues).

This is no longer working for me.
My config:
{
	// Use software rendering instead of hardware accelerated rendering.
	// This can help in cases where you see rendering issues in VS Code.
	// "disable-hardware-acceleration": true,
	"password-store": "gnome",
	// Allows to disable crash reporting.
	// Should restart the app if the value is changed.
	"enable-crash-reporter": false,
	// Unique id used for correlating crash reports sent from this instance.
	// Do not edit this value.
	...
}

What I see:

Same happening for me on Sway after upgrade to 1.86.0
I have "password-store": "gnome" in argv.json which no longer works.

I've just tried setting "gnome-libsecret" instead of "gnome" and everything works again!
@Android789515 can you try it too?

Hey @pavelxdd, your suggestion worked for me. Thank you!
However, I find it strange that the VS Code docs say this:

gnome: This option will first try the gnome-libsecret option implementation and then if that fails, it will fallback to the gnome-keyring option implementation.

This implies that the default behavior should work, but it doesn’t seem to.

Same happening for me just after upgrading to 1.86.0. Fixed by setting gnome-libsecret instead of gnome!

Fixed by setting gnome-libsecret instead of gnome here as well. Thank you!

I've just tried setting "gnome-libsecret" instead of "gnome" and everything works again! @Android789515 can you try it too?

This does not work for me.

I've just tried setting "gnome-libsecret" instead of "gnome" and everything works again! @Android789515 can you try it too?

It worked for me on Arch, thanks!

gnome-libsecret worked for me too

Still the same problem (on Manjaro).

Switching from gnome to gnome-libsecret seems to fix it for me, too:
Version: 1.86.0
Commit: 05047486b6df5eb8d44b2ecd70ea3bdf775fd937
Date: 2024-01-31T10:27:46.147Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.1.60-08594-g03a802b9a072

If you are in a situation where "password-store": "gnome" in argv.json no longer works, sorry for the breakage there was a behavior change in the runtime that got missed in the runtime update. Both gnome and gnome-keyring values are removed in favor of gnome-libsecret. We will prepare a candidate fix for 1.86.1 release.

On ChromeOS, I get that error too

~/.vscode/argv.json
// This configuration file allows you to pass permanent command line arguments to VS Code.
// Only a subset of arguments is currently supported to reduce the likelihood of breaking
// the installation.
//
// PLEASE DO NOT CHANGE WITHOUT UNDERSTANDING THE IMPACT
//
// NOTE: Changing this file requires a restart of VS Code.
{
	// Use software rendering instead of hardware accelerated rendering.
	// This can help in cases where you see rendering issues in VS Code.
	// "disable-hardware-acceleration": true,

	// Allows to disable crash reporting.
	// Should restart the app if the value is changed.
	"enable-crash-reporter": true,

	// Unique id used for correlating crash reports sent from this instance.
	// Do not edit this value.
	"crash-reporter-id": "d3649379-71f0-49b8-8896-22d26592c978",

	"password-store": "gnome",
}

malix@penguin:~$ sudo apt install gnome-keyring
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
gnome-keyring is already the newest version (42.1-1+b2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

malix@penguin:~$ code --verbose --vmodule="*/components/os_crypt/*=1"
[0205/162123.944602:ERROR:file_io_posix.cc(152)] open /home/malix/.config/Code/Crashpad/pending/c863bb7a-4d1c-4761-ac18-81dba03f53a8.lock: File exists (17)
[3708:0205/162124.111662:VERBOSE1:key_storage_util_linux.cc(52)] Password storage detected desktop environment: (unknown)
[3708:0205/162124.161114:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[main 2024-02-05T15:21:24.331Z] [File Watcher (node.js)] Request to start watching: /home/malix/.config/Code/User (excludes: <none>, includes: <all>, correlationId: <none>),/home/malix/.config/Code/User/settings.json (excludes: <none>, includes: <all>, correlationId: <none>)
[main 2024-02-05T15:21:24.365Z] Sending env to running instance...
[main 2024-02-05T15:21:24.367Z] [File Watcher (node.js)] Started watching: '/home/malix/.config/Code/User'
[main 2024-02-05T15:21:24.370Z] [File Watcher (node.js)] Started watching: '/home/malix/.config/Code/User/settings.json'
[3742:0205/162124.388037:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process.
[main 2024-02-05T15:21:24.505Z] Sent env to running instance. Terminating...
[main 2024-02-05T15:21:24.505Z] Lifecycle#kill()
[main 2024-02-05T15:21:24.505Z] Lifecycle#onWillShutdown.fire()

malix@penguin:~$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

VS Code Version: 1.86.0 - 05047486b6df5eb8d44b2ecd70ea3bdf775fd937 - x64
OS Version: ChromeOS Flex - Version 121.0.6167.155 (Official Build) beta (64-bit)

for vscode >= 1.86.0, set "password-store": "gnome-libsecret" in ~/.vscode/argv.json

Are there any resources on what other OS keyrings could be used other than gnome-keyring?

Breaking Fix
vscode >= 1.86.0 Set "password-store": "gnome-libsecret" in ~/.vscode/argv.json

gnome-libsecret is not a package I could find.  Do you mean libsecret?

For users who had "password-store": "gnome" stopped working, can you please help test whether it works again in the following build
VS Code Build: 59fb280
linux-arm64 linux-armhf linux-x64
Steps to test:

Extract and run the build with code-insiders --user-data-dir /tmp/test-argv-check
Set "password-store": "gnome" in argv.json
Confirm that authentication works as expected.

Can confirm that this build fixed the issue for me.

Can this be fixed for the infinite number of users having this problem? Seems like every time someone installs vscode he has to open this thread

@BlueskyFR this will be fixed in 1.86.1 released tomorrow.

Looks like an update has fixed the issue for me.
"password-store": "gnome-libsecret"

DE: Xfce 4.18
it's work:
yay -S gnome-keyring
kate ~/.vscode/argv.json and paste "password-store": "gnome-libsecret"
reboot
sync settings vscode
but I’m wondering if it’s possible to get rid of this problem altogether, why do we need a keychain in this editor, and is it possible to somehow simplify this action? if this is only needed to sync settings, then there must be an easier way

I'm using seahorse. Have you added the default "login" keystore? Not sure if it's needed. Added "password-store": "gnome-libsecret" and after collapsing the side nav bar it (the april release) no longer locks up and works (after overnight). VSCode should not be issuing git commands through the terminal session. VSCode should not be running /bin/python /home/jackokring/.vscode/extensions/ms-python.python-2024.4.0/python_files/printEnvVariablesToFile.py /home/jackokring/.vscode/extensions/ms-python.python-2024.4.0/python_files/deactivate/bash/envVars.txt in the terminal context.
Chromebook. arm64.

OS: Endeavouros 64
DE: Lxqt
need to add "password-store": "gnome-libsecret" to ~/.vscode/argv.json to fix this problem.

OS: Endeavouros 64 DE: Lxqt need to add "password-store": "gnome-libsecret" to ~/.vscode/argv.json to fix this problem.

i use "password-store": "basic",
it's work after reboot

I'm using Vscode 1.92.2 on Ubuntu 24.04 and had a similar issue where vscode would hang up when it tried to connect to the internet
This was the last line in the log before vscode hang up:
main 2024-08-26T14:13:58.031Z] [EncryptionMainService] Checking if encryption is available...

For me, "password-store": "basic" fixed it. Thanks @als-creator

I am using vscode on hyprland with kwallet. It isn't getting detected by default. Only works when i add this to runtime flags.
"password-store":"kwallet5"

Why isn't hyprland detected by default?

"The runtime arguments file 'argv.json' contains errors"
the error: "expected comma"


add Firefox support

refs #117
We can support Firefox by migrating FirefoxLauncher class from here into Dart code.
(I actually developed it in my personal project puppeteer-ruby )
puppeteer-dart currently doesn't have Launcher and Puppeteer class has such functionality, so I tried to create another puppeteer class as PuppeteerFirefox
Known issues:

Firefox often returns imcomplete payloads (some fields are null or {} or undefined...). Current protocol classes are assumed to be used with Chromium, and often throw cast errors with Firefox.
Firefox nightly is distributed with variours formats (.zip for Win64, .dmg for macOS, .tar.bz2 for Linux), and it is a little hard to support extracting all of them. (I always use Docker, and actually I don't use it... 😅 ) So in this implementation, executablePath is assumed to be required. (Downloader for Firefox is not implemented) IMPLEMENTED

example
Future<void> main() async {
  Logger.root.level = Level.ALL;
  Logger.root.onRecord.listen(print);

  final browser = await puppeteerFirefox.launch(
    headless: false,
    executablePath: '/Applications/Firefox Nightly.app/Contents/MacOS/firefox',
  );
  final myPage = await browser.newPage();

  // Go to a page and wait to be fully loaded
  await myPage.goto('https://www.google.com');

  // Do something... See other examples
  await myPage.click('input[name="q"]');
  await myPage.keyboard.type('puppeteer');

  await Future.wait([
    myPage.waitForNavigation(),
    myPage.keyboard.press(Key.enter),
  ]);

  await File('_google-puppeteer.png').writeAsBytes(await myPage.screenshot());

  await myPage.goto('https://detectmybrowser.com/');

  await File('_detect-my-browser.png').writeAsBytes(await myPage.screenshot());

  // Gracefully close the browser's process
  await browser.close();
}

_google-puppeteer.png:

_detect-my-browser.png

Hi @YusukeIwaki ,
Thank you for sharing your work. This is awesome.
The approach looks good to me. And I think it's ok to not have the download/extract part for Firefox.
The main issue is the incomplete/bad payload for firefox. It will require to modify the code generator to be more lenient.
It would also be good to run all the tests with Firefox.
Good job 👍

@xvrh Could you take a look at this PR?

Hi @YusukeIwaki
Sorry for the delay.
Thanks a lot for the hard work to find the small differences between chrome and Firefox.
@kendalsickels-wf maybe you are interested in trying this, since you opened #117
We cannot merge it as it because some of the files that you changed are generated from the protocol schema. We will need to  change the generator to include your changes.

Very sorry, I couldn't afford to fix the problems...
Now I already use Playwright for Firefox automation because the CDP implementation of Firefox is still really limited...
Please let me close this PR. I hope another Firefox user would contribute the Firefox support.


feat(storage-resize-images): added extension event for image resize completion

Adding events to the the storage-resize-image extension.

Codecov Report

Merging #967 (f1ab7c8) into next (4283a45) will decrease coverage by 0.03%.
The diff coverage is 28.58%.

:exclamation: Current head f1ab7c8 differs from pull request most recent head c89b653. Consider uploading reports for the commit c89b653 to get more accurate results

@@            Coverage Diff             @@
##             next     #967      +/-   ##
==========================================
- Coverage   47.16%   47.14%   -0.02%
==========================================
  Files          36       36
  Lines        1514     1519       +5
  Branches      220      224       +4
==========================================
+ Hits          714      716       +2
- Misses        799      802       +3
  Partials        1        1

Impacted Files
Coverage Δ

...torage-resize-images/functions/src/resize-image.ts
40.70% <0.00%> (ø)

storage-resize-images/functions/src/index.ts
28.13% <40.00%> (+0.66%)
:arrow_up:

firestore-send-email/functions/src/logs.ts
53.85% <0.00%> (ø)

Event is not published to eventarc and not abld to deploy as it is showing error stating that "type is invalid, http error 400"

@supratikkoley Could you please create an issue and provide some more details error log messages.

Kindly look into this issue #1042

Events for image resize completion is not generating. I have deployed an eventarc trigger, still it's not listening to any events generated by image-resize-extension.

Did you enable events when installing the extension? Did

@pavelgj  Yes..I enabled events while installing the extension and the channel is default.
This is the trigger function written by me -
exports.onimageresized = onCustomEventPublished("firebase.extensions.storage-resize-images.v1.complete",
  (event) => {
    functions.logger.info("Received image resize completed event", event);
});

Look at this Image. It's of eventarc firebase channel where the trigger function(created by me) was published.

(sorry need to get the obvious troubleshooting questions out of the way) have you verified that the extension works? Have you tried uploading images and observed resized images appear in storage?

@pavelgj  Yes, I verified the extension. It works fine. I uploaded an image and it resized the image (with new name prefxed with the SIZExSIZE)and deleted the original image.

Could you please verify that pubsub service account has access to the service account used by Eventarc to authenticate trigger function invocation has the necessary permissions? Here are the steps:

in the Eventarc UI in Cloud console go to the "Triggers" page and select the trigger for your function.
in the "details" there's a "Topic" with a link to the pubsub topic used for this trigger, click on the topic link
under "subscriptions" click on the subscription (ID) to navigate to the subscription details
click on "EDIT" at the top to edit the subscription
under "Delivery type" check that:

"Push" type is selected
"Enable authentication" is checked
<EMAIL_ADDRESS>service account is selected.
see if there's a warning message under the "service account" field (it usually says something like "Note: Cloud Pub/Sub needs the role roles/iam.serviceAccountTokenCreator granted to service account..."). If you see that warning press "GRANT" button.

@pavelgj  Okay...let me check. I will get back to you then. Thanks.

@pavelgj Thank you so much for this.  They really need this in the firebase documentation as it is very difficult to track down this issue when following the documentation.

@pavelgj Thank you so much for this. They really need this in the firebase documentation as it is very difficult to track down this issue when following the documentation.

@abierbaum did you experience this issue and had to follow steps from https://github.com/firebase/extensions/pull/967#issuecomment-1186171281?

@pavelgj Yes, I encountered it on two methods I added to one of my projects.  This comment was the only thing that allowed me to get everything working.  Thanks so much!!!

For my Image Resize cloud function I have already enabled events but I dont see any saved triggers on the EventArc interface. Do I have to manually create one? Because the following functions are never triggered:
exports.onimageresized = eventarc.onCustomEventPublished(
	'firebase.extensions.storage-resize-images.v1.onCompletion',
	(e) => {
		functions.logger.info('LOGGEr', e);
		console.log('EVENT', e);
	},
);
exports.eventhandler = eventarc.onCustomEventPublished(
	'firebase.extensions.storage-resize-images.v1.onSuccess',
	(e) => {
		functions.logger.info('eventhandler logger', e);
		console.log('EVENT onSuccess', e);
		// Handle extension event here.
	},
);

I tried both "onCompletion" and "onSuccess" methods.


Problem with VLAN in DFP-34X-2C2

I'm from Brazil, where I'm trying to use a DFP-34X-2C2 with the company "Oi Fibra" which in my region uses Nokia in the OLT and a Nokia G-140W-H in my residence.
I did all the clone procedure, GPON serial and etc and had O5 successfully.
My provider has two vLANs 210 for internet and 220 for phone/SIP.
However, according to the print below and my tests, only vLAN 220 works, where it is effectively accessed by vLAN 1899, however, vLAN 210 does not work.
Interestingly in "omcicli mib get 171" both vLANs 210 and 220 are displayed but in "omcicli mib get 84" only 1899 which is 220 works.
I've already changed the IGD and SFU firmwire, the type of router or bridge firmwire and I've tried all forms of configuration, however, the only vLAN that works is 1899/220, which is the voice/sip vLAN.
Could anyone help me with something to do?
PS. In other regions Oi Fibra uses Huawei and where it uses the DFP-34X-2C2 it works perfectly.
omcicli mib get 84
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
VlanTagFilterData
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
EntityID: 0xe102
FilterTbl[0]: PRI 0,CFI 0, VID 1899
FwdOp:  0x10
NumOfEntries: 1
=================================
EntityID: 0xe103
FilterTbl[0]: PRI 0,CFI 0, VID 1899
FwdOp:  0x10
NumOfEntries: 1
=================================
EntityID: 0xe10b
FilterTbl[0]: PRI 0,CFI 0, VID 1899
FwdOp:  0x10
NumOfEntries: 1
omcicli mib get 171
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
ExtVlanTagOperCfgData
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
EntityId: 0xe01
AssociationType: 10
ReceivedFrameVlanTagOperTableMaxSize: 0
InputTPID: 0x8100
OutputTPID: 0x8100
DsMode: 0
ReceivedFrameVlanTaggingOperTable
INDEX 0
Filter Outer   : PRI 8,VID 220, TPID 5
Filter Inner   : PRI 8,VID 4096, TPID 0, EthType 0x00
Treatment Outer   : PRI 15,VID 0, TPID 0, RemoveTags 1
Treatment Inner   : PRI 9,VID 1899, TPID 3
INDEX 1
Filter Outer   : PRI 15,VID 4096, TPID 0
Filter Inner   : PRI 8,VID 220, TPID 5, EthType 0x00
Treatment Outer   : PRI 15,VID 0, TPID 0, RemoveTags 1
Treatment Inner   : PRI 8,VID 1899, TPID 2
INDEX 2
Filter Outer   : PRI 8,VID 210, TPID 5
Filter Inner   : PRI 8,VID 4096, TPID 0, EthType 0x00
Treatment Outer   : PRI 15,VID 0, TPID 0, RemoveTags 1
Treatment Inner   : PRI 9,VID 1899, TPID 3
INDEX 3
Filter Outer   : PRI 15,VID 4096, TPID 0
Filter Inner   : PRI 8,VID 210, TPID 5, EthType 0x00
Treatment Outer   : PRI 15,VID 0, TPID 0, RemoveTags 1
Treatment Inner   : PRI 8,VID 1899, TPID 2
INDEX 4
Filter Outer   : PRI 15,VID 4096, TPID 0
Filter Inner   : PRI 15,VID 0, TPID 5, EthType 0x00
Treatment Outer   : PRI 15,VID 0, TPID 0, RemoveTags 3
Treatment Inner   : PRI 15,VID 0, TPID 2
INDEX 5
Filter Outer   : PRI 14,VID 4096, TPID 5
Filter Inner   : PRI 14,VID 4096, TPID 0, EthType 0x00
Treatment Outer   : PRI 15,VID 0, TPID 0, RemoveTags 3
Treatment Inner   : PRI 15,VID 4096, TPID 3
INDEX 6
Filter Outer   : PRI 15,VID 4096, TPID 0
Filter Inner   : PRI 14,VID 4096, TPID 5, EthType 0x00
Treatment Outer   : PRI 15,VID 0, TPID 0, RemoveTags 3
Treatment Inner   : PRI 15,VID 4096, TPID 2
AssociatedMePoint: 0x601
DscpToPbitMapping:
0x000000
0x249249
0x492492
0x6db6db
0x924924
0xb6db6d
0xdb6db6
0xffffff

This seems related to issue #26
It seems that both VLANs 210 and 220 end up as VLAN 1899 with different EntityIDs

this might help if using fix_vlan_tag on older firmware
https://github.com/Anime4000/RTL960x/tree/main/Firmware/DFP-34X-2C2#m110_sfp_odi_220817tar

this might help if using fix_vlan_tag on older firmware https://github.com/Anime4000/RTL960x/tree/main/Firmware/DFP-34X-2C2#m110_sfp_odi_220817tar

I already tried with this firmware too, don't works.
But I will use it again and post here to see if anything has changed on "omcicli" output.

Try setting FwdOp to 0x02 for each entityID Alone with the following commands then check for Internet then reboot after no connection
omcicli mib set 84 0xe102 FwdOp 0x02
Then check for connection on VLAN 1899
No connection reboot
then
omcicli mib set 84 0xe103 FwdOp 0x02
Then check for connection on VLAN 1899
No connection reboot
then
omcicli mib set 84 0xe10b FwdOp 0x02

Try setting FwdOp to 0x02 for each entityID Alone with the following commands then check for Internet then reboot after no connection omcicli mib set 84 0xe102 FwdOp 0x02 Then check for connection on VLAN 1899 and 210 No connection reboot then omcicli mib set 84 0xe103 FwdOp 0x02 Then check for connection on VLAN 1899 and 210 No connection reboot then omcicli mib set 84 0xe10b FwdOp 0x02

If "omcicli mib set 84 0xe102 FwdOp 0x02" only vLAN 1899 works, but only on 220 voice/SIP.
If "omcicli mib set 84 0xe103 FwdOp 0x02" WORKS! On vlan 1899.
If "omcicli mib set 84 0xe10b FwdOp 0x02" same result of first command, only 1899 on voice/SIP.
Is there a way to make this change permanent, resistant to reboot?

#!/bin/sh
VLAN Tag Fix: Fix VLAN wrong mapping
By inyourgroove
Additional VID check if config file is not empty by rajkosto
set -e
while true; do
for _EntityID in $(omcicli mib get 84 | grep '^EntityID:' | awk '{print $2}'); do
_FwdOp=$(omcicli mib get 84 ${_EntityID} | grep '^FwdOp:' | awk '{print $2}')

if [[ ! -z ${_FwdOp} && ${_FwdOp} != '0x02' ]]; then
  if [ -s " 0xe103" ]; then #only change FwdOp VIDs specified in the file
    _VlanId=$(omcicli mib get 84 ${_EntityID} | grep -o " VID [0-9]*" | awk '{print $2}')
if ! grep -o "\b${_VlanId}\b" "$configFname" > /dev/null; then
      continue
    fi
  fi

  omcicli mib set 84 ${_EntityID} FwdOp 0x02
fi

done
sleep 30
done

Maybe @Anime4000 or @rajkosto can chime in and make a custom script firmware for you.

Or you can DIY see this
https://github.com/Anime4000/RTL960x/tree/main/Tools/emulator
https://github.com/Anime4000/RTL960x/blob/main/Tools/etc/scripts/fix_vlan_tag.sh

Hi, may I suggest you to try @rajkosto's mod mod of the firmware M114_sfp_ODI_hybrid_220916 https://github.com/rajkosto/RTL960x/blob/main/Firmware/DFP-34X-2C2/M114_sfp_ODI_hybrid_220916F.tar ?
It's working for me and I have the same issue with other versions.
Also tried M110_sfp_ODI_220923FS with:
OMCI_CUSTOM_ME=32832
OMCI_CUSTOM_ME=65792
OMCI_VEIP_SLOT_ID=14

without success.
Only M114_sfp_ODI_hybrid_220916 is working with
flash set VLAN_CFG_TYPE 1
flash set VLAN_MANU_MODE 0

#107

omcicli mib set 84 0xe103 FwdOp 0x02

It didn't work for me, right now I'm studying how to make a custom that executes the command that works for my case automatically.
At this moment I have a script that runs on the router that automatically executes the command, but it is not ideal.

Or you can DIY see this https://github.com/Anime4000/RTL960x/tree/main/Tools/emulator https://github.com/Anime4000/RTL960x/blob/main/Tools/etc/scripts/fix_vlan_tag.sh

I customized the firmware "M110_sfp_ODI_220817.tar" by editing the script "fix_vlan_tag.sh" to run my customized command instead of the original script.
But unfortunately I don't have access to the voice/telephone vlan and still the DHCP gets the IP of the wrong vlan before the script runs and applies the fix.
I had to make a script that checks the IP obtained via DHCP, if it starts with 10. it renews to then obtain the correct internet IP.

I have exactly the same problem
I can’t for the life of me use the vlans provided by omcicli mib get 171. I can although use the one given by  omcicli mib get 84 by going to the web interface choose vlan - manual, save, then use transportation and save. The issue is that if the ONU reboots I have to go through these steps all over again which is not a practical solution.
Hope someone cal solve this issue soon


move all style elements to css files

There are inline styles that I'd like to move to outside css files.
However, I'm not sure if they should be in the main.css or in a new app.css file.
@ewelton this seems like alignment with either the main process or the renderer. Shouldn't the css all be in the renderer context?

Moved all style to the main.css. Doubt we will need another css file anytime soon.


Prerequisite PR for #28478 (Management of names of archived streams)

This pull request is a prerequisite for PR #28478. It addresses issues with the deactivation logic of streams and ensures that archived streams are properly restricted.

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@sanchi-t is this ready for buddy review?

@alya I just need few more minutes to add some comments in the PR.

@zulipbot label "buddy review".

@tnmkr Ready for review from you.

But I noticed that in this commit adding a reaction to a message in search result causes errors in dev environment while on main there are no errors.

Are you talking about this error?

I am getting this error on main branch when I add an emoji reaction

I am not sure how to manually test this since archived streams appearing in search is basically a bug.

Well you can make changes in get_active_streams function in models/streams.py and remove the deactivated=false line while filtering streams. This will make all the streams (including archived) to appear in the client. Then you can test it.

Can you elaborate a bit more on why this error log should be removed in this commit?
Looks like this state is still something that should never occur. I think it would be better to remove this log in the commit where we also change some behaviour such that this log becomes incorrect or irrelevant.

Yeah this state should never occur but since we don't send archived streams to the client but allow searching messages from archived streams, the adjusted_terms is null for archived stream messages. And clicking on the message from archived stream causes an error.
In the next PR #28478 we send archived streams to the client and there the adjusted_terms should never be null.

I am not sure. I am unable to reproduce that behaviour now either.
Regardless, this looks ready for next round of reviews to me!

@sanchi-t Please tag your mentor for review once conflicts are resolved.

@ryanreh99 ready for review from you.

Since this is a prerequisite PR, can we cherry pick commits from the original PR https://github.com/zulip/zulip/pull/28478.
the first commit could be moved here at the top - https://github.com/zulip/zulip/commit/3e4eb60efe3d84319b4932e475659807c155c0c6
Perhaps part of commit https://github.com/zulip/zulip/commit/8b0af0d2e6cc7ff307f93b844cb70980a960f4b3 could be moved here as well.

Done.

Can u check if there are any other code blocks which would cause no behavioral changes if merged and move it to this PR.

Yeah I cherry-picked 0d4aae5106e80ebd5e6d63ff5824b3ca396cc217

For the 4th commit, do we have backend validation for deactivated streams in message_send and message_edit ?
Please add unit tests in the same commit as well.

Validation is done access_stream_for_send_message and has_message_access before messages are sent or edited.
I have added the unit tests.

Also for the 2nd commit, im not sure whether this is a prep commit, as migration and other UI changed would need to be done before updating the exisiting logic.

In migration we are just removing prefix from deactivated streams, I don't think we need to do migration before fixing the logic. Also in this PR we fix the deactivating logic such that it dosen't mark the streams as private and the main PR #28478 we make sure that streams are not renamed. I think the migration has nothing to do with this PR.

Could you also mention the changes remaining in the other PR that are not in this one.

The other PR #28478 does following things:

Does not rename stream when archiving.
Send back archived stream to the client (The archived streams are included in unsubscribed streams list).
The archived streams are filtered out in stream settings>
(archived) suffix is shown after archived stream name.
Allows users with permissions to rename an archived stream when creating a new stream with the same name.

@zulipbot remove label "buddy review".

@zulipbot label "mentor review".

@zulipbot remove label "mentor review".

@zulipbot remove "mentor review".

@zulipbot label "maintainer review".

I stacked this into #28478 since I think we want to merge the changes together, dropping the semi-duplicate commit.


service_discovery: add telemetry

What does this PR do?

Adds telemetry for the service_discovery check.
Motivation

Get data on how the service_discovery check is performing/behaving.
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Additional code coverage is needed, too.

/merge


More Robust Error Handling

I've had a few issues this morning using the plugin. I'm happy to help debug, but I'm not sure exactly where I can find more information about the errors. Specifically, I've had the following happen to me:

Sometimes I can not even open a PR right after starting nvim - I get failed to fetch remote branch in what appears to be the 'fetching checks' stage.
When trying to open a PR while one is already open, I enter 'yes' and get the following error:

E5108: Error executing lua .../site/pack/packer/start/gh.nvim/lua/litee/gh/pr/init.lua:365: attempt to index field 'state' (a nil value)
stack traceback:
      .../site/pack/packer/start/gh.nvim/lua/litee/gh/pr/init.lua:365: in function 'close_pull'
      .../site/pack/packer/start/gh.nvim/lua/litee/gh/pr/init.lua:216: in function 'callback'
      ...er/start/dressing.nvim/lua/dressing/select/telescope.lua:58: in function 'run_replace_or_original'
      ...packer/start/telescope.nvim/lua/telescope/actions/mt.lua:65: in function 'key_func'
      ...k/packer/start/telescope.nvim/lua/telescope/mappings.lua:242: in function 'execute_keymap'
      [string ":lua"]:1: in main chunk

I also get the following error when trying to explicitly close an open PR:

Error executing Lua callback: .../site/pack/packer/start/gh.nvim/lua/litee/gh/pr/init.lua:365: attempt to index field 'state' (a nil value)
stack traceback:
        .../site/pack/packer/start/gh.nvim/lua/litee/gh/pr/init.lua:365: in function <.../site/pack/packer/start/gh.nvim/lua/litee/gh/pr/init.lua:344>

Ah, I assumed my gh config was correctly set to ssh. Setting that value correctly fixes the issues. Is there somewhere I can inspect the output of the commands? That would be helpful for debugging issues like this

yeah I think I could look into that. My first thought is to doing something like what null-ls does https://github.com/jose-elias-alvarez/null-ls.nvim/blob/main/lua/null-ls/logger.lua. I've flipped the debug flag on to diagnose issues with null-ls in the past

Looks cool. Im down for whatever. My only request is try to build something into litee.nvim or gh.nvim directly.
I have no problems with planetary, but we already require litee.nvim, and i dont want the depedencies to grow even further.

Think https://github.com/ldelossa/gh.nvim/pull/63 closes this issue.
It only logs cli interactions, but I think this is where 99.99% of the issues with gh.nvim creep up. Closing for now.


Remix v2_errorBoundary makes sign in 401 error

[X] Review the documentation: https://docs.clerk.com/
[X] Search for existing issues: https://github.com/clerkinc/javascript/issues
[X] Go through package changelog files.
[ ] Provide the Frontend API key from your application dashboard.

Package + Version

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[X] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore
[ ] other:

Dependencies + versions
{
  "dependencies": {
    "@clerk/remix": "^2.2.17",
    "@remix-run/node": "^1.14.3",
    "@remix-run/react": "^1.14.3",
    "@remix-run/vercel": "^1.14.3",
    "react": "^17.0.2",
    "react-dom": "^17.0.2"
  },
  "devDependencies": {
    "@remix-run/dev": "^1.14.3",
    "@remix-run/eslint-config": "^1.14.3",
    "@remix-run/serve": "^1.14.3",
    "@types/react": "^17.0.24",
    "@types/react-dom": "^17.0.9",
    "cross-env": "^7.0.3",
    "eslint": "^8.9.0",
    "prettier": "^2.5.1",
    "typescript": "^4.6.2"
  }
}

Browser/OS
Chrome 112
Description
https://github.com/arjunyel/remix-auth-starter/tree/bug/v2_errorBoundary
In remix.config.js, if v2_errorBoundary: true login results in a 401 error. v2_errorBoundary: false works fine.
v2_errorBoundary - Combine ErrorBoundary/CatchBoundary into a single ErrorBoundary https://remix.run/blog/future-flags

Oh wow, I am getting no error in the console and there are no headers on the failed request. But it happens 100% of the time for me (and in my other project). Are you signing in with Google? I am.
Any chance we can do a quick screen share in Discord since I can reproduce it 100% of the time? I am @arjunyel in the discord

Regular email password login works, but Google sign in throws the 401

x-clerk-auth-* response headers in the failed request with http 401
The reason the above is not visible is because you need to include those headers in response ( i forgot to mention it above 😅 ).
To do so you can use the following snippet in root.ts file:

import { getClerkDebugHeaders } from<EMAIL_ADDRESS>
export function headers({
  actionHeaders,
  loaderHeaders,
  parentHeaders,
}: {
  actionHeaders: Headers;
  loaderHeaders: Headers;
  parentHeaders: Headers;
}) {
  return {
    ...getClerkDebugHeaders(loaderHeaders),
  };
}

I managed to reproduce your issue but making the Clerk short lived session expire before refreshing the page.
I will also try the google sign-in flow and come back to you with more information.

Short answer
Supporting v2_errorBoundary flag, would require to export an ClerkErrorBoundary that will handle both CatchBoundary and ErrorBoundary .
We cannot make a quick fix at the moment because the implementation of such ClerkErrorBoundary would require to use useRouterError which is not supported by our minimum peer dependency of the @remix-run/react.
We have created an internal ticket for this and i will keep this issue open. Until we resolve this, i would suggest to avoid using the v2_errorBoundary flag. If it's a must have, i could provide a hack (but i would advise against it).
Extra information
There is special case in Clerk & SSR (eg when an expired session cookie is sent to server) where we do some magic to refresh the session and replay the request (we call it interstitial). In that case an http 401 is returned to the user (using the root CatchBoundary) with an html content.
In the case where v2_errorBoundary is set, the example code (stater template and your provided repo) is not correct since it uses the root level CatchBoundary instead of the the new ErrorBoundary which results in allowing the http 401 code with the interstitial magic to reach Browser and stuck there.

@dimkl thank you so much friend! I'll disable v2_errorBoundary for now

@dimkl latest version of Remix (1.15) will likely be the last before v2 and it now warns when not using the v2_errorBoundary flag. This should probably be addressed soon or not clerk customers will be able to upgrade to Remix v2.

FWIW, this should work as a temporary work around:
export function ErrorBoundary() {
  const error = useRouteError();
  if (isRouteErrorResponse(error)) {
    const { __clerk_ssr_interstitial_html } =
      error?.data?.clerkState?.__internal_clerk_state || {};
    if (__clerk_ssr_interstitial_html) {
      return (
        <html
          dangerouslySetInnerHTML={{ __html: __clerk_ssr_interstitial_html }}
        />
      );
    }
    return (
		//  Current CatchBoundary Component
    );
  }
  return (
    // Current ErrorBoundary Component
  );
}

@nicksrandall do you happen to know what the default CatchBoundary and ErrorBoundary components are?

Sorry, I don't know want you are referring to.

If used on root.tsx this would break the default catch-all component remix gives and just make the app crash. Do you happen to know how to manually put it in there? Otherwise I'll just add a small catch-all component and call it a day..

Thanks a lot!
This refactored code seems to work in case anyone needs it:
import {
  RemixRootDefaultCatchBoundary,
  RemixRootDefaultErrorBoundary,
} from "@remix-run/react/dist/errorBoundaries";

export const ErrorBoundary = () => {
  const error = useRouteError();
  if (isRouteErrorResponse(error)) {
    const { __clerk_ssr_interstitial_html } = error?.data?.clerkState?.__internal_clerk_state || {};
    if (__clerk_ssr_interstitial_html) {
      return <html dangerouslySetInnerHTML={{ __html: __clerk_ssr_interstitial_html }} />;
    }
    //  Current CatchBoundary Component
    return <RemixRootDefaultCatchBoundary />;
  } else if (error instanceof Error) {
    return <RemixRootDefaultErrorBoundary error={error} />;
  } else {
    let errorString =
      error == null
        ? "Unknown Error"
        : typeof error === "object" && "toString" in error
        ? error.toString()
        : JSON.stringify(error);
    return <RemixRootDefaultErrorBoundary error={new Error(errorString)} />;
  }
};

I can confirm that the current Clerk tutorial for Remix isn't working with current version of Remix, 1.15, and that adding the code above to root.jsx makes the app run again.

hello 👋
We will try to prioritise the changes to support v2 in the next couple of weeks.
In the meantime @clerk/remix is an open source package, if someone wants to contribute, feel free to open a PR and we will try to review it as soon as possible.

In the meantime can someone please add a note to the docs so others like me don't spend 2 days trying to figure out why Clerk is not working with their shiny new Remix app.

Hey everyone,
I have added this to your getting started guide so people know to disable it, thanks for the feedback!

I'd prefer to keep the configuration to disable it while we work on the improvements for V2.
We can discuss internally, if we want to put this in depending on the amount of time it will take us to add it to our SDK support.

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days.

Bump

Hello everyone! We just released<EMAIL_ADDRESS>which exports a V2_ClerkErrorBoundary (#1444) to be used by projects that have the v2_errorBoundary future flag set to true. The following code should replace the legacy CatchBoundary in root.tsx file:
export const ErrorBoundary = V2_ClerkErrorBoundary();

I'll be closing this issue as it's now resolved. Feel free to open another one if something comes up. Thank you!

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


No module named 'tensorflow.contrib' (Support for TF > 2.0)

Hi,
I have installed version 1.0.3 of easybert using pip.
$ pip3 install easybert
This downloads an old copy of the script, which is not compatible with the current Java version, because the older python version doesnt produce model.json, which is required by Java.
So to resolve this problem, I updated the code for bert,py from the source code.
When I execute the cli command:
$ bert download
I get the following errors:

bert/modeling.py", line 29, in

from tensorflow.contrib import layers as contrib_layers
ModuleNotFoundError: No module named 'tensorflow.contrib'

I have tensorflow version 2.7.0.
The fix for this is relatively simple, which I will leave here for others to follow, until the TF compliance can be upgraded.

edit the file: .local/lib/python3.8/site-packages/bert/modeling.py
Change line 29 to
from tensorflow_addons import layers as contrib_layers
install tensorflow_addons using
pip install tensorflow-addons
run the command again.

Then had to fix the problem with tf.session. I did this by editing the following lines in bert.py file
76: with tf.Session(graph=self._graph) as session:

76: with tf.compat.v1.Session(graph=self._graph) as session:

100: with self._session = tf.Session(graph=self._graph)

100: self._session = tf.compat.v1.Session(graph=self._graph)

137: with tf.Session(graph=self._graph) as session:

137: with tf.compat.v1.Session(graph=self._graph) as session:

173: with tf.Session(graph=self._graph) as session:

173: with tf.compat.v1.Session(graph=self._graph) as session:

205: with tf.Session(graph=bert._graph) as session:

205: with tf.compat.v1.Session(graph=bert._graph) as session:

212: with tf.Session() as session:

212: with tf.compat.v1.Session() as session:

Now the tf.placeholder issue
86: self._input_ids = tf.placeholder(name="input_ids", shape=(None, max_sequence_length), dtype=tf.int32)

86: self._input_ids = tf.compat.v1.placeholder(name="input_ids", shape=(None, max_sequence_length), dtype=tf.int32)

87: self._input_mask = tf.placeholder(name="input_mask", shape=(None, max_sequence_length), dtype=tf.int32)

87: self._input_mask = tf.compat.v1.placeholder(name="input_mask", shape=(None, max_sequence_length), dtype=tf.int32)

88: self._segment_ids = tf.placeholder(name="segment_ids", shape=(None, max_sequence_length), dtype=tf.int32)

88: self._segment_ids = tf.compat.v1.placeholder(name="segment_ids", shape=(None, max_sequence_length), dtype=tf.int32)

Next on to global_variables_initializer()
102: self._session.run(tf.global_variables_initializer())

102: self._session.run(tf.compat.v1.global_variables_initializer())

138: session.run(tf.global_variables_initializer())

138: session.run(tf.compat.v1.global_variables_initializer())

174: session.run(tf.global_variables_initializer())

174: session.run(tf.compat.v1.global_variables_initializer())

And saving.
167: tf.saved_model.simple_save(self._session, str(path), inputs={

167: tf.compat.v1.saved_model.simple_save(self._session, str(path), inputs={

176: tf.saved_model.simple_save(session, str(path), inputs={

176: tf.compat.v1.saved_model.simple_save(session, str(path), inputs={

206: bundle = tf.compat.v1.saved_model.load(session, ["serve"], str(path))

206: bundle = tf.compat.v1.saved_model.load(session, ["serve"], str(path))

I will edit this post with other changes I do to comply with TF > 2.0. Hopefully, this will be useful for someone else.

hi please check #37


Kitematic, error message : We couldn't find a native setup...

Expected behavior
Kitematic should launch without issue
Actual behavior
docker works well
Kitematic instantly displays this error message:
We couldn't find a native setup - Click the VirtualBox button to use VirtualBox instead or Retry to check again

Information about the Issue
I installed Docker Toolkit which came with Kitematic.
Docker version version 0.16.1, build cce350d7
thinks for yours messages

Same issue

Linux mint 19.3
Kitematic v0.17.11

@driss0hu , Reinstall docker and docker machine helps me

Same issue here

(Installed today) Ubuntu 20.04
Kitematic v 0.17.11-1

I had the same issue. I was able to fix it by adding my user to the docker group and rebooting my pc. Here is the link to the docker docs on how to do it. Hope it helps. https://docs.docker.com/engine/install/linux-postinstall/


BUG: Unable to select column with byte datatype

I am using python 3.6.9 to install Apache Superset and elasticsearch version 7.9.1. I have created doc with type as byte but I couldn't query the value in SQL LAB in a superset, getting the following error while querying,
Expected results
Select * from sample;
age    email                   name
10<EMAIL_ADDRESS>    6

what you expected to happen.
It should return the value
Actual results
elasticsearch error: 'byte'
what actually happens.
Showing Error: elasticsearch error: 'byte'
Screenshots

If applicable, add screenshots to help explain your problem.
How to reproduce the bug
Create index from Kibana,
PUT /sample
{
  "mappings": {
    "properties": {
      "age":    { "type": "integer" },
      "email":  { "type": "keyword"  },
      "name":   { "type": "byte"  }
    }
  }
}

PUT sample/_doc/1
{
  "age": "10",
  "email"<EMAIL_ADDRESS>  "name": "admin"
}

Go to 'Superset SQL Lab'
Click on 'SQL Editor'
Select Database
Select Schema
Select table (index: sample)
See an error

Environment
(please complete the following information):

superset version: Superset 0.37.2
python version: Python 3.6.9

CC: @dpgaspar

Superset server logs would help here. Those kinds of error are hard to debug if you dont have an ES cluster laying around...

I am getting the following error in superset while selecting the sample schema,
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): localhost:9200
INFO:werkzeug:<IP_ADDRESS> - - [09/Oct/2020 03:53:13] "GET /superset/extra_table_metadata/1/sample/default/ HTTP/1.1" 200 -
DEBUG:urllib3.connectionpool:http://localhost:9200 "POST /sample/_search?size=1 HTTP/1.1" 200 277
INFO:elasticsearch:POST http://localhost:9200/sample/_search?size=1 [status:200 request:0.006s]
DEBUG:elasticsearch:> None
DEBUG:elasticsearch:<<EMAIL_ADDRESS>DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): localhost:9200
DEBUG:urllib3.connectionpool:http://localhost:9200 "POST /_sql/ HTTP/1.1" 200 210
INFO:elasticsearch:POST http://localhost:9200/_sql/ [status:200 request:0.004s]
DEBUG:elasticsearch:> {"query":"SHOW COLUMNS FROM \"sample\""}
DEBUG:elasticsearch:< {"columns":[{"name":"column","type":"keyword"},{"name":"type","type":"keyword"},{"name":"mapping","type":"keyword"}],"rows":[["age","INTEGER","integer"],["email","VARCHAR","keyword"],["name","TINYINT","byte"]]}
WARNING:es.basesqlalchemy:Unknown type found byte reverting to string
INFO:werkzeug:<IP_ADDRESS> - - [09/Oct/2020 03:53:13] "GET /api/v1/database/1/table/sample/default/ HTTP/1.1" 200 -
Triggering query_id: 31
INFO:superset.views.core:Triggering query_id: 31
timeout can't be used in the current context
WARNING:superset.utils.core:timeout can't be used in the current context
signal only works in main thread
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/superset/utils/core.py", line 624, in __enter__
    signal.signal(signal.SIGALRM, self.handle_timeout)
  File "/usr/lib64/python3.6/signal.py", line 47, in signal
    handler = _signal.signal(_enum_to_int(signalnum), _enum_to_int(handler))
ValueError: signal only works in main thread
ERROR:superset.utils.core:signal only works in main thread
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/superset/utils/core.py", line 624, in __enter__
    signal.signal(signal.SIGALRM, self.handle_timeout)
  File "/usr/lib64/python3.6/signal.py", line 47, in signal
    handler = _signal.signal(_enum_to_int(signalnum), _enum_to_int(handler))
ValueError: signal only works in main thread
SQLite Database support for metadata databases will be removed             in a future version of Superset.
WARNING:superset.sql_lab:SQLite Database support for metadata databases will be removed             in a future version of Superset.
Query 31: Executing 1 statement(s)
INFO:superset.sql_lab:Query 31: Executing 1 statement(s)
Query 31: Set query to 'running'
INFO:superset.sql_lab:Query 31: Set query to 'running'
Query 31: Running statement 1 out of 1
INFO:superset.sql_lab:Query 31: Running statement 1 out of 1
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): localhost:9200
DEBUG:urllib3.connectionpool:http://localhost:9200 "POST /_sql/ HTTP/1.1" 200 146
INFO:elasticsearch:POST http://localhost:9200/_sql/ [status:200 request:0.011s]
DEBUG:elasticsearch:> {"query":"SELECT age,\n       email,\n       name\nFROM sample\nLIMIT 100"}
DEBUG:elasticsearch:< {"columns":[{"name":"age","type":"integer"},{"name":"email","type":"keyword"},{"name":"name","type":"byte"}],"rows":[[10,"admin@superset.com",6]]}
Query 31: <class 'KeyError'>
ERROR:superset.sql_lab:Query 31: <class 'KeyError'>
INFO:werkzeug:<IP_ADDRESS> - - [09/Oct/2020 03:53:13] "POST /superset/sql_json/ HTTP/1.1" 500 -

Closing this out since the issue has been sitting untouched for over two years. If you're still encountering such issues in current superset (e.g. master branch or 2.0.x) let us know, and we can either revisit or reopen this issue. Thanks!


🐛Deepmerge-ts now making typescript build hang / not responding

Bug Report
It's started since last week, when I try to compile my typescript,
tsc
something wrong happen, it never done. something is stuck.
I tried to reinstall all node_modules, clean NPM cache, lastly I uninstall my node and change to version 16.14.2
none of them works...
then today, I try to install all my dependencies one by one and see if the tsc running / atleast throwing error.
when it comes to remove deepmerge-ts. it works, my tsc throwing error module not found.
having dependency to deepmerge-ts:

after removing

I tried with all version deepmerge-ts@3, @2, and @1, none of them work...
deepmerge-ts is awesome library that I need for my project, I hope it can be solved.
Expected behavior
Won't affect to tsc compiler behavior
Actual behavior
It make tsc compiler stuck
Steps to reproduce

npm i deepmerge-ts
npm run build or tsc
getting stuck

System Environtment

OS: Windows 11
NodeJS: 16.14.2, 14.17.6
Typescript: 4.4.2, 4.4.4, 4.6.3
npm: 6, 8.5

Files:
tsconfig.json:
{
	"compileOnSave": true,
	"compilerOptions": {
		"composite": true,
		"baseUrl": "./",
		"outDir": "./lib",
		"declaration": true,
		"declarationDir": "./@types",
		"declarationMap": true,
		"target": "ES6",
		"module": "CommonJS",
		"lib": [
			"ES6",
			"ES2018",
			"ESNext",
			"DOM"
		],
		"strict": true,
		"strictPropertyInitialization": false,
		"noImplicitAny": false,
		"noImplicitThis": false,
		"pretty": true,
		"sourceMap": true,
		"allowJs": true,
		"noEmit": false,
		"moduleResolution": "node",
		"allowSyntheticDefaultImports": true,
		"forceConsistentCasingInFileNames": true,
		"esModuleInterop": true,
		"experimentalDecorators": true,
		"emitDecoratorMetadata": true,
		"useUnknownInCatchVariables": false,
		"removeComments": true,
		"typeRoots": [
			"src/@types",
			"node_modules/@types"
		]
	},
	"include": [
		"src/**/*.ts"
	],
	"exclude": [
		"dist",
		"lib",
		"node_modules",
		"tests",
		"*deprecated*",
		"*ignore*"
	]
}

I forked the repo, https://github.com/fatihaziz/deepmerge-ts-es6/compare/main...fix/ts-issue-es6
and now somehow its working fine, no more hang or not responding.
but, I still don't know the reason behind it, why the tsc compiler become not responding...
Could I upload this into npm?

Give me a bit and I'll see if I can resolve this.
Would you be able to provide a minimal repo that reproduces the issue?

this is the minimal repo: here

Just started looking into this now.
I haven't found the exact cause of the problem yet but the issue goes away it you use "skipLibCheck": true in your project's tsconfig.json

If we set the skipLibCheck: true typescript compiler will ignore descrepancy from the dependencies types.
Typescript server won't bother checking the types error from modules anymore. Which we won't like to do.
I think the problem is from the v04 types generated by rollup. But i never use rollup before, so i dont know what the purpose of it.

What I've found so far it that it seems to be this type declaration that is causing the hang.
https://github.com/RebeccaStevens/deepmerge-ts/blob/4b6b64dad22a6a926a2343ed914f6fbeb282bff1/dist/node/types/current/index.d.ts#L389
I don't know why yet.

Maybe its goes like this:

deepmerge-ts types which generated is occuring a loophole for typescript compiler.
No error when compiling on the deepmerge-ts side.
then, when it published. someone install it, and try to compile it, the typescript will fall into the loophole.
And the compiler stuck.

Its weird and mindblowing for me since how types can make the compiler fall into indefinitely loophole.
This is indicated by my laptop performance when i try to compile it, the fan speed rise up higher than usually.
Which it rarely happen on normal build, that indicates there is some resource intensive task when compiling.
I try to make indefinitely while loop and run on browser and have same indication.

I'm trying to debug tsc atm to see what is going on. It's possible this is an upstream problem with TypeScript itself.

Alright, i will wait for the updates then.

So I'm not sure exactly what is going on but I think it is to do with the type complexity.
The type shouldn't actually be that complex, it should be aliased.


Inconsistent dependency on the money model in Cicero

Describe the bug
While Accord Project templates have been moved to use the more recent<EMAIL_ADDRESS>model, Cicero code still indirectly imports the older model.cto through the payment obligation in the runtime.cto model https://github.com/accordproject/models/blob/eb02be31874e1e078b144dabb85d15f93fdd8e87/src/cicero/runtime.cto#L19

Because of that dependency, in theory we should have re-published the runtime model as a version 0.2.0 but republishing core models is very intrusive to the stack.

This should now be resolved, with the publication of new base models.


Calendar wrong order and duplicate events

When editing an event that's back to back with another, they swap places.
When editing a single instance of a recurring event in a google calendar accessed using an ical the bot will show both the new and old messages.

Testing shows duplicate events only happen when time is edited


Create script + docs to assist with forks

What was wrong?
Forking is error prone and undocumented.
How was it fixed?
To-Do

[ ] Clean up commit history

[ ] Add entry to the release notes

Cute Animal Picture

towncrier --draft

towncrier

@a1love Did you mean to tell us something?


XRDP can not load cpu integrated graphics(amd renoir)

first of all, please understand that there may be grammatical errors because my native language is not English.
My apu is amd 4300u apu(and no discrete graphics ) so I need to use Linux kernel 5.8 or over. I choose debian bullseye testing version and use unstable source to had overcame most of my issues related with amd apu.
Only remain issue(at this moments) is when I connect my debian server via xrdp, xrdp session can not recognized my integrated graphics.
When I try to connect with external monitor, GNOME recognize my graphics as a "AMD Renoir" and It working smoothly, but xrdp is not.
My expectation is that the GNOME settings screen shows the graphic as "AMD renoir", but it shows "llvmpipe".

inxi -Fxz shows like below.

xrdp / Xorg package version like below.

It seems all driver installed well, but I don't know what is the problem.
If this isn't an issue, just a lack of technical understanding, I would also appreciate it if you let me know a forum that could help.

Sorry we didn't get round to commenting on this.
This is normal behaviour. The AMD driver works with the local screen only. Also, the Debian xorgxrdp package doesn't enable glamor by default, so Mesa is the best you can get.


Nick: Watch wendigodistribution.com

Nick requests the watch of the watch_keyword wendigodistribution\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

wendigodistribution\.com has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by Ryan M in Charcoal HQ


Issue with button embedded in link embedded in form in v3

Issue occurs in the following scenario:
<form>
  <a href="/foo/bar">
    Click me!

    <button style="display:none">Check Out With PayPal</button>
  </a>
</form>

Clicking on the "Click me!" link ends up triggering the link click, because the target element is assumed to be the form.

Fixed and ready for push.


Defined indexes for container not being picked up once deployed

Hi there,
Using the template from these docs, I've found that the indexes defined within the indexes array in the template aren't being applied to the deployed instance.
This is how I have it:
{
"indexingMode": "consistent",
"automatic": true,
"includedPaths": [{
"path": "/*",
"indexes": [
{
"kind": "Range",
"dataType": "number",
"precision": -1
},
{
"kind": "Range",
"dataType": "string",
"precision": -1
}
]
}
]
}
But this is what I see in the deployed instance in the "settings" tab in the portal:
{
"indexingMode": "consistent",
"automatic": true,
"includedPaths": [
{
"path": "/*",
"indexes": []
}
]
}
Is this a bug, or are the docs wrong?
Thanks,
Ed

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

ID: cecb9c8e-133d-065b-314f-ff173f74a3d6
Version Independent ID: 0d9926b1-569f-d4af-ba21-609393e6d7fc
Content: Create and manage Azure Cosmos DB using Azure Resource Manager templates
Content Source: articles/cosmos-db/manage-sql-with-resource-manager.md
Service: cosmos-db
GitHub Login: @markjbrown
Microsoft Alias: mjbrown

@edfreeman Thank you for your feedback! We will review and provide an update as appropriate.

@edfreeman Thank you for pointing that issue.
I am able to reproduce the same behaviour.
@markjbrown Could you please help here.

We made a recent back end change in our indexing engine that defaults to range index for both strings and numbers with a precision of -1. The ARM templates and docs have not yet been updated to reflect this as the default values. If you make non-default changes to your indexing policy, for instance, adding spatial indexing, they will be reflected in your deployed container.
Apologies for the confusion. We are working on updating all of our samples now.
Thanks.

Thanks @markjbrown
@edfreeman We will proceed to close this issue now.
If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

Thanks, both!

So indexes does not apply at the moment or they just don't show up at portal. Tried to add spatial indexing.
Thanks you!

@ytsymbaliuk. If you make any non-default changes to your indexing policy, they will be reflected in the portal.
thanks.


Roundtrip refactor into MVC

When working on expanding the roundtrip functionality I ran into some issues with the current implementation details of the JavaScript code:

It was very monolithic and relied significantly on global scoped variables.
The management of data and the drawing of the view were intermixed making it difficult to add new functionality which relied on adjusting positioning data of the charts.
Some code was redundant and could be eliminated by making greater use of D3's data binding properties.

To solve these problems and others, I refactored much of this codebase in an Model View Controller design pattern (a commonly used pattern that works well with visualization or UI heavy code). To accomplish this I moved code into several classes:

Model
Views

MenuView
ChartView
TooltipView

Controller

The Model stores and manages all data associated with the visualization. It also keeps track of some context relevant states the visualization may be in. For our visualization purposes, it keeps track of and updates node data. After certain data values are updated it will dispatch a request that all views do a re-rendering cycle.
The three views do not manipulate data at all and use D3 to make intelligent decisions of what should and should not be updated when a call to their respective rendering functions is made. By separating each view into its own class it improves the modularity of the codebase and makes it easy to identify where a snippet of code might be. Interaction with the view is managed by D3 and dispatches requests to the controller class.
The controller class acts as a router for user-driven events. When a user clicks on an interactive element, information about that interaction is transmitted to the controller class which then calls relevant data-updating functions in the model.

Changes included in #389.


Extra indentation on EJS statements

Hello very helpful plugin thank you.
Is there a way to also indent EJS statements and the html tags that are wrapped by them? They seem to stack on top of each other.
Similar to this indentation: (which is replaced on save)

Yep, same question here...

thank you!
Originally I was having trouble with EJS formatting, and when I ran js-beautify with the erb template, it felt pretty good.
Please take a moment to find out what happens with the js-beautify settings.

Hi,
thank you - I looked through the js-beautify options and used "templating": ["erb"] but couldn't find a way to indent EJS code blocks (e.g. the line following an opening bracket "{ %>", as requested here)

I'm sorry.
I reread the source code of js-beautify and investigated what the settings did not work for ... Unfortunately, there was no setting that gave good results.
The idea seems to be to match the indentation of the HTML that is ultimately rendered by the client as much as possible, rather than what it looks like in the code.
When formatted in the expected format

    <% a.array.forEach(element=> { %>
      <% if (condition) { %>

            <%- element.name %>

      <% } else { %>

            <%- element.age %>

      <% } %>

    <% }); %>

HTML rendered in the browser.
In this case, the indentation of the HTML tag will be broken.

            neko

            10

The result of formatting by ejs-beautify

    <% a.array.forEach(element=> { %>
    <% if (condition) { %>

        <%- element.name %>

    <% } else { %>

        <%- element.age %>

    <% } %>

    <% }); %>

In this case, the indentation of the HTML rendered in the browser will be clean.

        neko

        10

I know how you feel!
Unlike the source code before compiling, the latter seems to be more correct when considering the formatting of the generated HTML.
It is not easy to judge which is correct. It's difficult ... 😅

thank you!
As one of the ideas, it would be interesting to switch between coding view and rendering view ... whether or not it can be done 😅

Hi @HiroyukiNIshimura is it possible that you modify js-beautify to format its code to indent the ejs specific code otherwise its really hard to read even if the indentation of the output html tags are broken

even if its just an option that defaults to false


fix(image): switch to adoptopenjdk/openjdk11:alpine-jre

You may want to test this as I didn't have a chance to build Doplarr and test it.

Adoptopenjdk (my preferred JDK) has JRE builds for alpine that are half the side of the openjdk:11 image at 50MB
adoptopenjdk/openjdk11:alpine-jre

But  switching to alpine means I need to understand all the apt stuff you did haha

I can do it in Alpine. I'll update this PR.

So you also want doplarr to be built in the image? There's methods to do this that can still keep a light image.

Do you also want doplarr to be built in the image? There's methods to do this that can still keep a light image.

I don't think we need to. Github CI is building it and copying the JAR in and I don't think I need to debug in the image anymore.

@kiranshila updated, please verify :)

Thanks! Looks great!