| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
This PR has been closed automatically. This repo only keeps pull requests open when they come from a maintainer, or from a contributor a maintainer has assigned to the linked issue, and you aren't currently assigned to #3174. If a maintainer assigns you to #3174, this PR reopens on its own and there's nothing more you need to do here. Assignment is a maintainer call based on capacity; comments that only ask to be assigned don't factor in. What does help is engaging on the issue itself by confirming the repro, explaining why it matters for your use case, or describing the approach you'd take. You're welcome to keep pushing commits here (just avoid force-pushing, since GitHub can't reopen a rewritten branch), but that on its own won't get the PR reviewed or the issue assigned, and realistically most auto-closed PRs stay closed. There's no need to open a new PR either way. CONTRIBUTING.md has the full reasoning, but in short:
Maintainers: reopen, remove missing-issue-link, or add bypass-issue-check to override. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
Client OpenTelemetry spans did not record JSON-RPC error responses because ErrorData was converted to MCPError after the span context exited. This made failed client requests indistinguishable from successful requests in telemetry.
This change records StatusCode.ERROR, error.type, and rpc.response.status_code while the client span is still active. The existing MCPError behavior is unchanged.
Tests
AI assistance was used during development, and the change was reviewed and verified locally.
Fixes #3174