Native server raises an error "Ruff received invalid settings from the editor" when navigating into installed packages:

[MichaReiser]

Native server raises an error "Ruff received invalid settings from the editor" when navigating into installed packages:

2025-04-23 11:17:15.804281841  WARN No settings available for file:///usr/local/lib/python3.12/site-packages/cv2/__init__.py - falling back to default settings
2025-04-23 11:17:15.804285127 ERROR Failed to load settings from `configuration`: error looking key 'workspaceFolder' up: environment variable not found

This loses the rules, and causes flickering and constant popups as it refreshes frequently.

ruff-lsp behaves much better with just a quiet warning.

[Warn  - 11:20:42 AM] Skipping standard library file: /usr/local/lib/python3.12/site-packages/cv2/__init__.py

Originally posted by @brad-phobos in astral-sh/ruff#15991 (comment)

[dhruvmanila]

@brad-phobos Thanks for reporting! Can you share your VS Code settings for Ruff? It seems that somewhere workspaceFolder is not being expanded which is something the extension should already do. Or, is it that you're using a different syntax like $workspaceFolder instead of ${workspaceFolder}?

[brad-phobos]

        "ruff.importStrategy": "fromEnvironment",
        "ruff.configuration": "${workspaceFolder}/../Tools/ruff.toml",

I am inside a devcontainer if that matters

[dhruvmanila]

I am inside a devcontainer if that matters

Do you see the same issue outside devcontainer?

Can you also provide debug logs from both the extension and the server? Refer to https://github.com/astral-sh/ruff-vscode#troubleshooting for more info.

[dhruvmanila]

Nevermind, I'm able to reproduce this just fine on the VS Code extension.

[dhruvmanila]

Ok, somehow I'm seeing the ${workspaceFolder} in the global client settings which is causing this to fail:

2025-04-29 15:48:05.407556000  INFO global settings: ClientSettings {
    configuration: Some(
        String(
            "${workspaceFolder}/formatter/ruff.toml",
        ),
    ),

[dhruvmanila]

Oh right, the global settings doesn't expand these variables because they don't have a reference i.e., the workspace that these settings belong to.

[dhruvmanila]

We resolve these variables in ruff.interpreter, ruff.configuration, ruff.path, ruff.lint.args (deprecated), ruff.format.args (deprecated). Apart from the deprecated settings, for the other settings, I think we'd need to remove the values which contain variables would be specific to a workspace which are ${workspaceFolder}, ${workspaceFolder:...} (where ... is the workspace name for a multi-root workspace). Other variables doesn't seem specific to a workspace:

ruff-vscode/src/common/settings.ts

Lines 86 to 122 in ab433c4

	function resolveVariables(
	value: string | string[],
	workspace?: WorkspaceFolder,
	): string | string[] | null {
	const substitutions = new Map<string, string>();
	const home = process.env.HOME || process.env.USERPROFILE;
	if (home) {
	substitutions.set("${userHome}", home);
	}
	if (workspace) {
	substitutions.set("${workspaceFolder}", workspace.uri.fsPath);
	}
	substitutions.set("${cwd}", process.cwd());
	getWorkspaceFolders().forEach((w) => {
	substitutions.set("${workspaceFolder:" + w.name + "}", w.uri.fsPath);
	});
	for (const [key, value] of Object.entries(process.env)) {
	if (value !== undefined) {
	substitutions.set("${env:" + key + "}", value);
	}
	}
	if (typeof value === "string") {
	let s = value;
	for (const [key, value] of substitutions) {
	s = s.replace(key, value);
	}
	return s;
	} else {
	return value.map((s) => {
	for (const [key, value] of substitutions) {
	s = s.replace(key, value);
	}
	return s;
	});
	}
	}