Skip to content

Fix exp seeding to be after bucket creation#1717

Merged
deep1401 merged 1 commit intomainfrom
fix/seed-ordering
Apr 1, 2026
Merged

Fix exp seeding to be after bucket creation#1717
deep1401 merged 1 commit intomainfrom
fix/seed-ordering

Conversation

@deep1401
Copy link
Copy Markdown
Member

@deep1401 deep1401 commented Apr 1, 2026

No description provided.

@paragon-review
Copy link
Copy Markdown

paragon-review bot commented Apr 1, 2026

Paragon Summary

This pull request review analyzed 1 file and found no issues. The review examined code changes, potential bugs, security vulnerabilities, performance issues, and code quality concerns using automated analysis tools.

Paragon did not detect any problems in the current diff. Proceed with merge after your normal checks.

This PR changes startup order so experiment seeding runs only after the required bucket has been created, preventing seed-time failures caused by missing storage. It makes initial server setup and boot more reliable.

Key changes:

  • Moved experiment seeding to run after bucket creation on server startup.
  • Fixed startup initialization order in api/scripts/on_server_start.py.
  • Prevents seeding from occurring before required storage buckets exist.

Confidence score: 5/5

  • This PR has low risk with no critical or high-priority issues identified
  • Score reflects clean code review with only minor suggestions or no issues found
  • Code quality checks passed - safe to proceed with merge

1 file reviewed, 0 comments


Tip: @paragon-run <instructions> to chat with our agent or push fixes!

Dashboard

@sentry
Copy link
Copy Markdown

sentry bot commented Apr 1, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@deep1401 deep1401 merged commit 0174c48 into main Apr 1, 2026
13 checks passed
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.

2 participants