anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Indefinitely retry to fetch #2039

New Issue
Open
opened 2026-02-16 17:33:53 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 17:33:53 -05:00
Owner
Copy Link
Copy Source

Originally created by @falentio on GitHub (Oct 10, 2025).

Originally assigned to: @rekram1-node on GitHub.

when fetching url, and url returning status 404 (unsafe status for retry), sometimes it just do indefinitely amount of retry.

Image
Originally created by @falentio on GitHub (Oct 10, 2025). Originally assigned to: @rekram1-node on GitHub. when fetching url, and url returning status 404 (unsafe status for retry), sometimes it just do indefinitely amount of retry. <img width="1920" height="1048" alt="Image" src="https://github.com/user-attachments/assets/4911337c-32ac-4cbe-93ff-13b6e301cbf9" />
yindo commented 2026-02-16 17:33:53 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Oct 10, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #452: More resilient retry policy for Amazon Bedrock rate limiting - discusses retry mechanisms and suggests more resilient retry policy instead of just trying 3 times
  • #1712: Implement exponential back-off when hitting rate limits - specifically mentions exponential back-off with auto-retry to keep agent loop running
  • #833: handle LLM overload errors (e.g. {"type": "overloaded_error", "message": "Overloaded"}) - proposes retry logic with limits to avoid infinite loops, very similar concept
  • #1321: Implement retry with backoff - directly mentions implementing retry with backoff functionality

These issues all discuss implementing better retry mechanisms with proper backoff strategies to avoid the exact problem you're experiencing with indefinite retries on 404 status codes.

Feel free to ignore if none of these address your specific case with 404 status codes and URL fetching.

@github-actions[bot] commented on GitHub (Oct 10, 2025): This issue might be a duplicate of existing issues. Please check: - #452: More resilient retry policy for Amazon Bedrock rate limiting - discusses retry mechanisms and suggests more resilient retry policy instead of just trying 3 times - #1712: Implement exponential back-off when hitting rate limits - specifically mentions exponential back-off with auto-retry to keep agent loop running - #833: handle LLM overload errors (e.g. {"type": "overloaded_error", "message": "Overloaded"}) - proposes retry logic with limits to avoid infinite loops, very similar concept - #1321: Implement retry with backoff - directly mentions implementing retry with backoff functionality These issues all discuss implementing better retry mechanisms with proper backoff strategies to avoid the exact problem you're experiencing with indefinite retries on 404 status codes. Feel free to ignore if none of these address your specific case with 404 status codes and URL fetching.
yindo commented 2026-02-16 17:33:53 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Oct 10, 2025):

edit: wow yeah ill fix this

@rekram1-node commented on GitHub (Oct 10, 2025): edit: wow yeah ill fix this
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2039
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?