Repository navigation
fix(cli): show what the server answered when an assertion fails - #60
Merged
Merged
Conversation
A failing flow printed the same error four times followed by the whole flag
reference, and never said what came back. It now prints one line:
Error: assertion failed: response.status == 200 (got 401: {"error":"Invalid credentials"})
- node.AssertionError adds the status, and for a non-2xx response a
one-line body excerpt (200 chars); 2xx bodies stay out of CI logs since
they can carry tokens. Used by the request and GraphQL nodes.
- flow run silences cobra usage once arguments are valid; argument
errors still print it.
- The root command prints errors once and exits 1; the runner's duplicate
error log is now debug-level.
Claude-Session: https://claude.ai/code/session_01DTfHLHkkg1TPGQgj6P6grg
Contributor
📊 Performance ComparisonGenerated on 2026-10-07 15:47:36 UTC Detailed Results
📈 Summary Statistics
✅ Stable Performance: All benchmarks within acceptable range |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A failing flow printed the same error four times, then the whole flag reference, and never said what came back. It now prints one line:
node.AssertionErroradds the status. For a non-2xx response it also adds a one-line, 200-char body excerpt. 2xx bodies are left out of CI logs, since they can carry tokens. Used by the request and GraphQL nodes.flow runsilences cobra usage once arguments are valid; argument errors still print usage.cli: patch.Verified: new
assert_error_test.go,server:test, CLI tests,server:lint,cli:lint,root:lint:format,client:lint. Also checked by hand with a built binary against a real 401.🤖 Generated with Claude Code
https://claude.ai/code/session_01DTfHLHkkg1TPGQgj6P6grg