Expose project scope in local server errors - #517
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 4948a14. Configure here.
d3c7ff9 to
e1dbf66
Compare
5fbaee3 to
c2c2303
Compare
|
what about if we check for the presence of a .clickhouse dir in the CWD when a local command is run - and if there isn't one - we can tailor the output to give the message that we dont search for parent .clickhouse dirs must be run from project root |
|
I think this belongs in this PR rather than a separate issue: it directly improves project-scoped server errors. We should keep it narrow to commands that require existing project state, such as |
|
Superseded by #559 in stack #563. |

Summary
server list,stop, andremovelookup, metadata, and state failures.clickhousedirectories are not searched and provide fixed recovery commands for running and stopped serversprojectfield; keep project paths in command output only and out of telemetry.clickhousestate, and symlinked working directories without adding a new--projectflagCloses #477
Tests
cargo fmt --all --checkcargo build -p clickhousectlcargo check -p clickhousectl --no-default-featurescargo test -p clickhousectl(633 unit tests plus all integration suites)cargo clippy -p clickhousectl --all-targets -- -D warningsStack
issue-472-atomic-server-metadata)