Skip to content

Fall back to official image mirrors when ECR Public throttles CI - #341

Merged
dipeshbabu merged 1 commit into
mainfrom
ci/registry-fallback
Nov 19, 2026
Merged

dipeshbabu merged 1 commit into
mainfrom
ci/registry-fallback

Conversation

@dipeshbabu

Copy link
Copy Markdown
Owner

CI on main failed again after #340: ECR Public returned 429 Too Many Requests on all four build attempts over three minutes, so retrying the same registry is not enough.

The Docker deployment smoke now:

  • builds from the same official `python` tag, trying ECR Public, then `mirror.gcr.io/library`, then Docker Hub in each round, with 30s/90s backoff between rounds;
  • pre-pulls `postgres:16-alpine` with the same fallback and tags it under the ECR name used by `.github/docker-compose.ci.yml`.

Both mirror tags were verified to resolve on mirror.gcr.io. docs/CI.md describes the fallback. Pull failures from every source still fail CI.

🤖 Generated with Claude Code

Retrying ECR Public alone was not enough: it returned 429 for every
attempt over three minutes. The deployment smoke now tries the same
official Python and Postgres tags from ECR Public, mirror.gcr.io and
Docker Hub in each round, backing off between rounds, and tags the
Postgres image under the name the CI Compose override expects.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Nov 19, 2026

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@github-actions

Copy link
Copy Markdown

AgentLoop replay self-test

This required repository check evaluates generated synthetic demo traces. It tests the replay and CI machinery; it does not show that this PR improves application performance.

AgentLoop CI Report

  • Status: passed
  • Replay: Replay passed: latency improvement 69.67%, cost improvement 78.82%, retry delta -1.
  • Merge recommendation: synthetic self-test only; assess application traces before merge
  • Findings: 1 total, 0 high severity, 1 patchable

Performance Gates

Gate Status Detail
latency_regression pass 0.00% regression <= 0.00% allowed
cost_regression pass 0.00% regression <= 0.00% allowed
latency_improvement pass 69.67% improvement >= 20.00% required
cost_improvement pass 78.82% improvement >= 5.00% required
retry_non_increase pass 0 candidate retries <= 1 baseline retries

Trace inputs

This comparison includes synthetic data. It does not establish application performance gains from a pull request.

Side Run ID Path Synthetic marker Source
baseline run_1546764c1c114704 runs/research_agent_baseline.json yes agentloop_demo
candidate run_ca78f653035442ca runs/research_agent_optimized.json yes agentloop_demo

Metric Impact

Metric Impact
Latency improvement 69.67%
Cost improvement 78.82%
Retry delta -1
Candidate schema validity not provided
Candidate quality score not provided

Top Findings

Finding Severity Type Rewrite
al_cache_context_a45d97d7c9e8: Cache repeated prompt/context prefix medium cache_context Move stable instructions into cached prefixes, summaries, or framework-level memory instead of resending full text.

@dipeshbabu
dipeshbabu merged commit 693709d into main Nov 19, 2026
25 checks passed
@dipeshbabu
dipeshbabu deleted the ci/registry-fallback branch November 19, 2026 00:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant