-
Notifications
You must be signed in to change notification settings - Fork 31
avoid panic on client disconnect #176
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
base: main
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Welcome @ask-elad! It looks like this is your first PR to volcano-sh/agentcube 🎉 |
Summary of ChangesHello @ask-elad, 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 addresses a critical bug where the router would experience a panic and subsequent crash when a client disconnected during a long-running agent invocation. By introducing a targeted recovery mechanism for Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. 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 addresses a panic that occurs when a client disconnects during a long-running operation by recovering from http.ErrAbortHandler. The approach is sound and correctly handles the specific panic from httputil.ReverseProxy. My review includes one high-severity comment regarding a potential nil pointer dereference within the new recover block, which could lead to a panic within a panic. I've recommended adding a defensive nil check to improve robustness.
3ac5cb2 to
4ff2eec
Compare
|
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #176 +/- ##
==========================================
+ Coverage 35.60% 35.67% +0.06%
==========================================
Files 29 29
Lines 2533 2562 +29
==========================================
+ Hits 902 914 +12
- Misses 1505 1521 +16
- Partials 126 127 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: Aryan Rai <aryanrai746@gmail.com>
4ff2eec to
e8f3cad
Compare
| } | ||
| return | ||
| } | ||
| panic(r) |
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.
why do you call panic, this is not recommended in production
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.
BTW, donot we have recovery middleware
v1.Use(gin.Recovery())
What type of PR is this?
/kind bug
What this PR does / why we need it:
This PR fixes a router panic that occurs when a client disconnects during a long running agent invocation.
The router uses httputil.ReverseProxy to forward requests, and when the client times out or disconnects, the standard library panics with http.ErrAbortHandler. This panic was previously unhandled, causing the router to crash and Gin to emit recovery warnings.
The change treats client disconnects as a normal early exit by catching http.ErrAbortHandler at the proxy boundary, preventing the router from panicking while preserving existing behavior for all other error cases.
Which issue(s) this PR fixes:
Fixes #78
Special notes for your reviewer:
Additionally tests can be written for this in a new pr if this is fine
Does this PR introduce a user-facing change?:
NONE