direnv: Environment updated. Restart extensions?

[AlecRust]

With this extension installed, every time I start vscode, I get this:

If I press the "Restart" button, it just pops up again a second later.

I have direnv installed via Homebrew, but I do use asdf-direnv, perhaps that's loading it too fast causing this issue?

Any ideas? Here's my full shell setup.

[mkhl]

i'm sorry, i have no idea 😔

[mkhl]

i managed to reproduce something like this, i think by opening a workspace where some variables get unset. will try to fix it now

[mkhl]

could you check if the extension built in https://github.com/direnv/direnv-vscode/actions/runs/3307828818 helps?

[AlecRust]

Thanks for looking at this @mkhl. Trouble is this no longer seems as frequent as when I first opened this issue, so I'm struggling to reliably reproduce this on the current extension version. It does still happen though.

Changes in #263 look good regardless though, will you be merging that/cutting a release?

[mkhl]

Changes in #263 look good regardless though, will you be merging that/cutting a release?

yes absolutely

[codygman]

I get this error with direnv extension version 0.10.1 and code 1.71.2 on an m1 mac installed from https://code.visualstudio.com/ and the output says:

[2022-11-30 12:50:50.781] [renderer1] [error] A provider has already been registered for scheme file: Error: A provider has already been registered for scheme file
    at k.registerEditSessionIdentityProvider (vscode-file://vscode-app/private/var/folders/_4/2gfm39j97zl8bztn5gzwdjqm0000gr/T/AppTranslocation/1EA2F780-B5E7-4CA1-9607-10A27017CBA7/d/Visual%20Studio%20Code%202.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2766:14678)

[codygman]

Okay it's not happening anymore after:

• disabling all extensions
• restarting code
• removing .envrc and .direnv
• starting code and going back to my workspace
• re-enabling direnv extension
• calling reset and reload direnv from command palette

I'm not sure which of those things resolved the issue or why, but that's what I did.

[claviola]

I've been suddenly getting a lot of pop-ups like these on my own install. Is there anything I can look into to see the root cause?

[mkhl]

There's a direnv output you can look at (the "Output" tab in the bottom panel, then select "direnv" from the dropdown on the right), it logs which variables are getting modified.

[janeklb]

There's an option to automatically restart the extension

Direnv > Restart: Automatic
[ ] Automatically restart extension host upon environment changes

that might "fix the problem" (ie. make the dialog stop showing up), but it's got me wondering: why does the extension need to restart when it detects environment changes?

[mkhl]

why does the extension need to restart when it detects environment changes?

many other extensions use the environment on activation.
restarting the extension host gives us a chance to modify the environment before they use it.

[janeklb]

oh -- this is referring to restarting the VSCode extension host (not the direnv extension itself). that makes a lot more sense 🙇🏻 thanks!