fix: suppress retry logs in version command when SpiceDB unavailable #564
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #554
When running
zed versionwith an unavailable SpiceDB instance, the command would retry multiple times and log noisy error messages that cluttered the output.Changes
versioncommand (setsmax-retries=0)--max-retriesif explicitly setChangedstate to preserve flag semanticsservice: (unknown)for consistent output formatBefore
After
Test Plan
TestVersionCommandWithUnavailableServerto verify silent fallback--max-retriesis still respected