Fix illegal invocation error and restore sentry #47
Conversation
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
Co-authored-by: punitsai36 <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Cursor Agent can help with this pull request. Just |
Correct @sentry/cloudflare withSentry invocation order and fix formatting to resolve Illegal invocation errors and re-enable monitoring in Workers.
Swap argument order back to (options, handlers) which the SDK expects, while keeping formatting fix applied.
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.
Fix Sentry wrapper invocation order to resolve "Illegal invocation" errors and restore observability.
The previous PR incorrectly ordered arguments for
Sentry.withSentry, causing Cloudflare Workers to throw "Illegal invocation" errors and disabling Sentry monitoring for scheduled, queue, and fetch handlers. This change corrects the argument order toSentry.withSentry(handlers, optionsResolver).