Flood of processes

[pavelzherdin]

Hi, I'm wondering if I'm doing something wrong here. I installed the extension, didn't change any settings. I have latest mise.

If I add something like this in either mise.toml of some project currently opened in vscode, or global mise config.toml

[env]
WTF="{{ exec(command='ls')}}"

I will get a flood of ls processes that would keep growing until I remove that line.

I'm using bash, mise is activated in .bashrc with

eval "$($HOME/.local/bin/mise activate bash)"

[hverlin]

Hi @pavelzherdin, thank you for reporting this issue.

Unfortunately, I cannot reproduce the issue you are facing.
Do you have additional information about your setup?

For example, can you run mise doctor from VSCode (command palette ⇾ Mise: Open Menu ⇾ Select the mise doctor action) and paste the result here (feel free to remove anything sensitive). Maybe also take a look at the extension logs, in case you see any errors.

[hverlin]

If I run the extension in dev. mode, it does not happen 🤯
Seems quite difficult to debug unfortunately

[pavelzherdin]

I think this is somehow related to interactive/login/non-login shells, but I don't know enough about those and their differences. Will try to poke around some more later.

[hverlin]

What is surprising is that I get different results in dev mode or when the extension is installed. (set the command to sleep 10). With Help ⇾ Process explorer

With the extension installed

In dev mode:

[hverlin]

I think in the case of the dev mode, it might be because when I run mise dev, mise is launching vscode which might set some variables that avoids the recursive mise hook-env calls

[pavelzherdin]

I didn't come up with anything that could explain this. But, it's possible to start vscode with a script like this to trigger the issue

# Reset shell level
SHLVL=0 

# Set minimal environment
SHELL=/bin/bash

# Launch VSCode
/usr/share/code/code

With SHLVL=2 things would be fine, and that was the difference in env between starting vscode from terminal and through the app lanucher. I didn't read up on what this var means yet, but at least it may allow starting vscode in debug mode.