Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36642
cca55a7c cleanup(core): tighten the daemon environment spec The negative getDaemonSpawnEnv assertion passed even without the undefined guard (an undefined-valued property still satisfies toBeUndefined), so assert the key is absent instead. The convergence test failed for developers with JAVA_TOOL_OPTIONS exported because the captured payload carried the shell value; delete it before capturing. Move the MISE_SHELL assertion to the shell-session test to match the grouping in the exclusion list.
by Leosvel Pé...
Succeeded
36642
96a3ebfb fix(core): exclude volatile shell and editor env vars from the daemon The daemon invalidates its cached project graph whenever any forwarded env var differs from the previous client's, including vars deleted because the new client lacks them. Per-command shell-integration vars (atuin's ATUIN_HISTORY_ID), per-directory vars (PWD, INIT_CWD), and terminal/editor identity vars that differ between clients sharing one daemon (TERM_PROGRAM, GIT_ASKPASS, the VS Code extension-host vars) therefore forced a full graph recompute on every invocation or whenever terminal and IDE clients alternated. Exclude those from the reflected daemon environment: exact entries for presentation, terminal-identification, per-invocation, and VS Code extension vars; prefix entries for shell integrations (ATUIN_, STARSHIP_, MCFLY_, DIRENV_, __MISE_), Electron, and AI harness session vars; and a new pattern list for Windows' pid-shaped EFC_ vars. Functional inputs (PATH, GIT_DIR, CHROME_BIN, COPILOT_HOME, FNM_DIR, MISE_ENV) stay forwarded. The env used to spawn the daemon keeps ELECTRON_RUN_AS_NODE via the new getDaemonSpawnEnv() so an Electron-hosted client (Nx Console) can still start the daemon with its own execPath. Exact and pattern exclusions now take precedence over the prefix-exclusion overrides, so a future exact "never send" entry for an allow-listed var cannot be silently ignored.
by Leosvel Pé...
Failed
36642
Flaky task→
96a3ebfb fix(core): exclude volatile shell and editor env vars from the daemon The daemon invalidates its cached project graph whenever any forwarded env var differs from the previous client's, including vars deleted because the new client lacks them. Per-command shell-integration vars (atuin's ATUIN_HISTORY_ID), per-directory vars (PWD, INIT_CWD), and terminal/editor identity vars that differ between clients sharing one daemon (TERM_PROGRAM, GIT_ASKPASS, the VS Code extension-host vars) therefore forced a full graph recompute on every invocation or whenever terminal and IDE clients alternated. Exclude those from the reflected daemon environment: exact entries for presentation, terminal-identification, per-invocation, and VS Code extension vars; prefix entries for shell integrations (ATUIN_, STARSHIP_, MCFLY_, DIRENV_, __MISE_), Electron, and AI harness session vars; and a new pattern list for Windows' pid-shaped EFC_ vars. Functional inputs (PATH, GIT_DIR, CHROME_BIN, COPILOT_HOME, FNM_DIR, MISE_ENV) stay forwarded. The env used to spawn the daemon keeps ELECTRON_RUN_AS_NODE via the new getDaemonSpawnEnv() so an Electron-hosted client (Nx Console) can still start the daemon with its own execPath. Exact and pattern exclusions now take precedence over the prefix-exclusion overrides, so a future exact "never send" entry for an allow-listed var cannot be silently ignored.
by Leosvel Pé...
Succeeded
36642
38e80a32 fix(core): exclude volatile shell and editor env vars from the daemon The daemon invalidates its cached project graph whenever any forwarded env var differs from the previous client's, including vars deleted because the new client lacks them. Per-command shell-integration vars (atuin's ATUIN_HISTORY_ID), per-directory vars (PWD, INIT_CWD), and terminal/editor identity vars that differ between clients sharing one daemon (TERM_PROGRAM, GIT_ASKPASS, the VS Code extension-host vars) therefore forced a full graph recompute on every invocation or whenever terminal and IDE clients alternated. Exclude those from the reflected daemon environment: exact entries for presentation, terminal-identification, per-invocation, and VS Code extension vars; prefix entries for shell integrations (ATUIN_, STARSHIP_, MCFLY_, DIRENV_, __MISE_), Electron, and AI harness session vars; and a new pattern list for Windows' pid-shaped EFC_ vars. Functional inputs (PATH, GIT_DIR, CHROME_BIN, COPILOT_HOME, FNM_DIR, MISE_ENV) stay forwarded. The env used to spawn the daemon keeps ELECTRON_RUN_AS_NODE via the new getDaemonSpawnEnv() so an Electron-hosted client (Nx Console) can still start the daemon with its own execPath. Exact and pattern exclusions now take precedence over the prefix-exclusion overrides, so a future exact "never send" entry for an allow-listed var cannot be silently ignored.
by Leosvel Pé...
Failed
36642
Flaky task→
38e80a32 fix(core): exclude volatile shell and editor env vars from the daemon The daemon invalidates its cached project graph whenever any forwarded env var differs from the previous client's, including vars deleted because the new client lacks them. Per-command shell-integration vars (atuin's ATUIN_HISTORY_ID), per-directory vars (PWD, INIT_CWD), and terminal/editor identity vars that differ between clients sharing one daemon (TERM_PROGRAM, GIT_ASKPASS, the VS Code extension-host vars) therefore forced a full graph recompute on every invocation or whenever terminal and IDE clients alternated. Exclude those from the reflected daemon environment: exact entries for presentation, terminal-identification, per-invocation, and VS Code extension vars; prefix entries for shell integrations (ATUIN_, STARSHIP_, MCFLY_, DIRENV_, __MISE_), Electron, and AI harness session vars; and a new pattern list for Windows' pid-shaped EFC_ vars. Functional inputs (PATH, GIT_DIR, CHROME_BIN, COPILOT_HOME, FNM_DIR, MISE_ENV) stay forwarded. The env used to spawn the daemon keeps ELECTRON_RUN_AS_NODE via the new getDaemonSpawnEnv() so an Electron-hosted client (Nx Console) can still start the daemon with its own execPath. Exact and pattern exclusions now take precedence over the prefix-exclusion overrides, so a future exact "never send" entry for an allow-listed var cannot be silently ignored.
by Leosvel Pé...