-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Retry eval tasks if API instability detected #9365
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
Review complete. Found 2 issues to address:
Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues. |
| logger.close() | ||
|
|
||
| if (isApiUnstable) { | ||
| throw new Error("API is unstable, throwing to trigger a retry.") |
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.
User-aborted tasks should not trigger retries. If a task is aborted (likely user-initiated at line 303-305), the retry will be triggered anyway when API instability is detected. Consider checking taskAbortedAt to prevent retrying intentionally cancelled tasks.
Fix it with Roo Code or mention @roomote and request a fix.
Important
Detects API instability in
runTask()and triggers a retry if instability is detected by monitoring specific events.runTask()inrunTask.tsby monitoringapi_req_retry_delayedandapi_req_retriedevents.isApiUnstableflag totrueif instability detected.runTask()ifisApiUnstableistrueto trigger retry.api_req_retry_delayedandapi_req_retriedtologgableSaysand monitors them inTaskEventhandler.This description was created by
for 603a60f. You can customize this summary. It will automatically update as commits are pushed.