Add alpha-engine-data to boot-pull REPOS on ae-trading#55
Merged
Conversation
Today's OOM fix moved DailyData from ae-dashboard (t3.micro) to ae-trading (t3.small) but boot-pull.sh's REPOS list was never updated. Result: alpha-engine-data is checked out on the instance but never refreshes on boot, so commits merged to origin/main never reach the DailyData SSM step. Confirmed gap today while sequencing the daily_data health-stamp rollout (alpha-engine-data#41 → alpha-engine#54): HEAD on the instance was 0728d95 while origin/main was 4a14d0b. A tactical manual pull brought Friday's run up to date; this commit makes it automatic going forward. No code-path changes on Friday's run either way — the list is append-only and boot-pull already handles missing .git dirs gracefully (SKIP log, no error). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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
Closes a deployment-plumbing gap introduced by today's OOM fix. When DailyData was moved from ae-dashboard (t3.micro) to ae-trading (t3.small), `boot-pull.sh`'s `REPOS` array was never updated. Net result: `alpha-engine-data` is checked out on the trading instance but never refreshes on boot, so commits merged to origin/main silently don't reach the DailyData SSM step.
How this surfaced
Sequencing the daily_data health-stamp rollout:
Tactical manual `git pull` already run to unblock Friday; this PR prevents the class-of-bug from recurring.
Change
One-line append to the `REPOS=( ... )` array. `boot-pull.sh` already handles missing `.git` directories gracefully (`SKIP` log, no error), so this is safe even if alpha-engine-data isn't cloned on other instances.
Test plan
Blocks
Audit opportunity (not in scope)
Other instances may have the same drift. Worth auditing ae-dashboard's boot/lifecycle scripts for similar stale REPOS lists — if any repo moved between instances post-deployment, its auto-pull plumbing needs to move with it.
🤖 Generated with Claude Code