Repository navigation
fix(cli): exit non-zero when feedback submission is rejected - #1766
Merged
Dumbris merged 1 commit intoOct 26, 2026
Merged
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Dumbris
approved these changes
Oct 26, 2026
Dumbris
left a comment
Member
There was a problem hiding this comment.
Verified: the PR test fails on main for the reason described and passes on this branch merged with main; race tests for the touched packages and CI lint (bare and server tags) are clean. Also built and tested together with the rest of this batch, independently reviewed, and cross-reviewed with a second model.
Member
|
Merged. Thank you, @rudycelekli! |
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
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.
Bug
mcpproxy feedbackexits 0 when the submission was not accepted.SubmitFeedbackreturnsSuccess: falsewithout an error in two cases: the backend answers 2xx with{"success": false, "error": "..."}, or it answers a non-JSON 3xx.runFeedbackprints "Feedback submission failed: ..." (in text mode) and then returnsnil. In-o jsonmode it prints the JSON and also returnsnil. Scripts and CI wrappers therefore treat a rejected submission as sent.Trigger
With the telemetry endpoint returning
200 {"success":false,"error":"rejected by backend"}:Fix
After rendering the output, return
feedback submission failed: <error>whenresp.Successis false, so the exit code is non-zero in both text and JSON modes. The text branch no longer prints its own failure line, because cobra prints the returned error. The success path is unchanged.Test
TestRunFeedback_RejectedSubmissionReturnsErrorpoints the telemetry endpoint at anhttptestserver that returns{"success":false}, and asserts thatrunFeedbackreturns an error.Commands run
go vet ./cmd/mcpproxy: cleango test -count=1 ./cmd/mcpproxy: ok (needs cgo; run withSDKROOTset to the macOS 26.5 SDK locally)runFeedback returned nil for a submission the backend rejected.gofmt -lon the edited files: no output