Conversation
Member
Author
|
bugbot run |
Contributor
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit a9ba625. Configure here.
mr-danya
pushed a commit
to mr-danya/sentry-mcp
that referenced
this pull request
Oct 6, 2026
…#1420) This PR fixes an issue where `sentry event view` would fail with a `ResolutionError` when an issue short ID (e.g., `PRODUCTION-RCP-API-A9R`) was passed as the second positional argument (e.g., `sentry event view <org>/<project> PRODUCTION-RCP-API-A9R`). The root cause was that `parsePositionalArgs` in `packages/cli/src/commands/event/view.ts` correctly checked `looksLikeIssueShortId(first)` for the first argument but lacked a corresponding check for `looksLikeIssueShortId(second)`. The fix adds this missing check. Now, when an issue short ID is detected as the second argument, `parsePositionalArgs` returns `{ eventId: LATEST_EVENT_SENTINEL, targetArg: first, issueShortId: second }`, allowing the command to correctly resolve the latest event for that issue, preventing the misleading "is not a valid ID" error. Fixes [CLI-1EJ](https://sentry.sentry.io/issues/7437967683/?seerDrawer=true) --------- Co-authored-by: sentry[bot] <39604003+sentry[bot]@users.noreply.github.com> Co-authored-by: jared-outpost[bot] <jared-outpost[bot]@users.noreply.github.com>
mr-danya
pushed a commit
to mr-danya/sentry-mcp
that referenced
this pull request
Oct 6, 2026
…#1420) This PR fixes an issue where `sentry event view` would fail with a `ResolutionError` when an issue short ID (e.g., `PRODUCTION-RCP-API-A9R`) was passed as the second positional argument (e.g., `sentry event view <org>/<project> PRODUCTION-RCP-API-A9R`). The root cause was that `parsePositionalArgs` in `packages/cli/src/commands/event/view.ts` correctly checked `looksLikeIssueShortId(first)` for the first argument but lacked a corresponding check for `looksLikeIssueShortId(second)`. The fix adds this missing check. Now, when an issue short ID is detected as the second argument, `parsePositionalArgs` returns `{ eventId: LATEST_EVENT_SENTINEL, targetArg: first, issueShortId: second }`, allowing the command to correctly resolve the latest event for that issue, preventing the misleading "is not a valid ID" error. Fixes [CLI-1EJ](https://sentry.sentry.io/issues/7437967683/?seerDrawer=true) --------- Co-authored-by: sentry[bot] <39604003+sentry[bot]@users.noreply.github.com> Co-authored-by: jared-outpost[bot] <jared-outpost[bot]@users.noreply.github.com>
mr-danya
pushed a commit
to mr-danya/sentry-mcp
that referenced
this pull request
Oct 6, 2026
…#1420) This PR fixes an issue where `sentry event view` would fail with a `ResolutionError` when an issue short ID (e.g., `PRODUCTION-RCP-API-A9R`) was passed as the second positional argument (e.g., `sentry event view <org>/<project> PRODUCTION-RCP-API-A9R`). The root cause was that `parsePositionalArgs` in `packages/cli/src/commands/event/view.ts` correctly checked `looksLikeIssueShortId(first)` for the first argument but lacked a corresponding check for `looksLikeIssueShortId(second)`. The fix adds this missing check. Now, when an issue short ID is detected as the second argument, `parsePositionalArgs` returns `{ eventId: LATEST_EVENT_SENTINEL, targetArg: first, issueShortId: second }`, allowing the command to correctly resolve the latest event for that issue, preventing the misleading "is not a valid ID" error. Fixes [CLI-1EJ](https://sentry.sentry.io/issues/7437967683/?seerDrawer=true) --------- Co-authored-by: sentry[bot] <39604003+sentry[bot]@users.noreply.github.com> Co-authored-by: jared-outpost[bot] <jared-outpost[bot]@users.noreply.github.com>
This branch was successfully deployed
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.
removes everything related to the sentry shared formatter, no real behavioral change since the flag was turned off in the Sentry side so the shared formatter wasn't used.
get_issue_detailsstill returnsstructuredContent, now built from the MCP's own data.deleted:
?llmFormat=json/?llmFormat=markdownparams on the event and autofix requests.formattedfield on the event and autofix schemas.usesSharedFormatterBodyandwrapSeerContent, and the code that used them inget_issue_details,analyze_issue_with_seerandformatIssueOutput.structuredContent:
event.bodyis now the MCP's own markdown for the event (formatEventOutput), not a parsed formatter payload. Transactions get the structured path too, with their performance trace in the body.event.messageandresponseNotesfields, so the structured result carries everything the markdown output shows. The markdown output and the structured payload build their notes with the same function.