-   Notifications  You must be signed in to change notification settings 
- Fork 218
feat: add async error handling to onRequest #1755
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
BREAKING CHANGE: Unhandled errors in async onRequest handlers now immediately return a 500 Internal Server Error instead of hanging until timeout. This may affect clients relying on 504 Gateway Timeout for retry logic.
| Summary of ChangesHello @taeold, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the reliability of HTTP request handlers by implementing robust error handling for asynchronous operations. It introduces a common utility to catch unhandled errors and rejected promises within  Highlights
 Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either  
 Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a  Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
 | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces an important improvement by adding a safety net for unhandled errors in async onRequest handlers. The new withErrorHandler wrapper correctly catches both synchronous errors and rejected promises, preventing requests from hanging and instead returning a 500 error. The implementation is clean and applied correctly to both v1 and v2 onRequest functions. The new tests cover the basic success and failure scenarios. I've added a couple of suggestions to make the tests more comprehensive by asserting the HTTP response status and body in the error case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is great! might save devs some $$ too if we're preventing long hangs to timeout
We'll now wraps an HTTP handler with a safety net for unhandled errors.
This wrapper catches both synchronous errors and rejected Promises from
asynchandlers. Without this, an unhandled error in anasynchandler would cause the request to hang until the platform timeout, as Express (v4) does not await handlers.This is a BREAKING CHANGE in the most technical sense - unhandled errors in async onRequest handlers now immediately return a 500 Internal Server Error instead of hanging until timeout. This may affect clients relying on timeouts (for whatever reason).