Repository navigation
Conversation
Fixes getsentry#25481 Co-Authored-By: Cursor <cursoragent@cursor.com> Co-authored-by: Rahul Kashyap <itisrmk@users.noreply.github.com>
itisrmk
requested review from
JPeer264 and
mydea
and removed request for
a team
October 18, 2026 00:51
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 57293ad. Configure here.
Co-Authored-By: Cursor <cursoragent@cursor.com> Co-authored-by: Rahul Kashyap <itisrmk@users.noreply.github.com>
This branch has not been 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.

Hapi accepts
server.route({ method })as a string or an array of strings, and only expands an array into one route per method after instrumentation has already wrapped the handler. The wrapper closed over that array, so withtraceLifecycle: 'static'it calledroute.method.toUpperCase()and threw, turning the request into a 500. The same array was also stored onhttp.request.method.The wrapped handler now reads the single method Hapi has resolved on the request and uses that uppercase value for the static span name and
http.request.method. Routes registered with a string method are unchanged.Tests: added unit coverage in
packages/server-utilsand an array-method case to the Hapi node integration suite (ESM and CJS).yarn lintandyarn testpass.yarn lint) & (yarn test).Fixes #25481
This change was prepared with AI assistance.