fix(aws-serverless): guard against negative timeout warning delay#19932
fix(aws-serverless): guard against negative timeout warning delay#19932james-suvera wants to merge 2 commits intogetsentry:developfrom
Conversation
Semver Impact of This PR🟢 Patch (bug fixes) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨Deps
Bug Fixes 🐛Cloudflare
Core
Deps
Other
Internal Changes 🔧Deps Dev
Other
🤖 This preview updates automatically when you update the PR. |
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.
|
This pull request has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you apply the label |
|
Closing due to inactivity after stale warning. Comment or reopen when ready to continue, and use |

Node 24 warns if a negative timeout is set. This is possible if
tryGetRemainingTimeInMillisreturns0(fallback) andoptions.timeoutWarningLimitis set. Less likely, but could also happen with very hightimeoutWarningLimitvalue. In this scenario the timeout warning is pointless and therefore should be skipped