Repository navigation
forward-test: pace GDELT requests 20 s apart - #7
Merged
Merged
Conversation
Both live runs at a 6 s pace lost 6 of 20 names to GDELT 429s (or a timeout) even after the retry pass. Space first-pass requests 20 s apart and retry-pass requests 30 s apart; about 7 minutes for 20 names, inside the existing 40-minute budget and 60-minute job timeout. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HTqzkhjyuhZZun8Az1tW6C
Deploying aetherius with
|
| Latest commit: |
9343b16
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a38e86be.aetherius-7cp.pages.dev |
| Branch Preview URL: | https://claude-laughing-gates-gmc4fm.aetherius-7cp.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
What changed? In
simulations/forward_test/run_forward_test.py, GDELT requests in the first pass now wait 20 s between companies (was 6 s), and the retry pass waits 30 s (was 15 s). The 40-minute budget and the 60-minute job timeout are unchanged. The forward-test README explains why.Why was this needed? Both live runs so far lost 6 of 20 names even after the retry pass: GDELT throttles GitHub's shared runners.
Retrying harder doesn't help; spacing requests out should. At about 20 s each, 20 names take roughly 7 minutes.
Validation
pytest -q aetherius/tests): 122 passed. The retry and budget tests use a fake clock and still hold at the new pacing.ruff check aetherius simulations scripts).simulations/forward_test/README.md.Worst case: if every request is refused, the budget stops new requests at 40 minutes. The last in-flight request can take up to about 3 minutes with its internal retries, plus about 1 minute for EDGAR, so the run still ends under the 60-minute job timeout.
Scope
aetherius/app/services/...)simulations/backtest/...)Forward test only.
Safety Checklist
.env, API keys, tokens)simulations/artifacts/, runtime logs)Notes for Reviewers
Generated by Claude Code