fix: rebuild CUDA image to patch CVEs, migrate to multi-stage build - #14
Merged
Conversation
- Migrate Dockerfile.cuda from single-stage Ubuntu 22.04 to multi-stage Ubuntu 24.04 (devel builder + runtime final), reducing image from 8.6GB to ~5GB and CVEs from 80 (6 HIGH) to 9 (0 HIGH) - Adopt industry-standard CUDA tag convention: :cu130, :version-cu130 - Auto-detect VERSION from latest git tag in Makefile - Update README with new CUDA tags and driver requirements (>= 550) - Update docker-compose.cuda.yml and portainer-stack-cuda.yml Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
You have used all of your free Bugbot PR reviews. To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial. |
dvcdsys
added a commit
that referenced
this pull request
May 14, 2026
Two related migration-safety fixes:
1. migrateSplitWorkspaceRepos used to commit the DB tx first and
then rename clone dirs — a kill -9 in that window left old
{workspace_repos.id} dirs orphaned and forced a re-clone. Now
the rename runs BEFORE the transaction and an error aborts the
migration (leaves workspace_repos in place so the next run
retries). Counters for renamed / skipped_missing_source /
skipped_target_exists / failed are logged on completion.
2. Add schema_migrations(version, name, applied_at). Open() reads
MAX(version) and skips already-applied migrations. Existing
prod DBs bootstrap by detecting which legacy tables are present.
3. Migration test suite expanded with subtests covering partial
rename, pre-existing target, missing source dir, duplicate
project_path rows, and idempotent re-runs.
Resolves Fix #3, #7, #14.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
dvcdsys
added a commit
that referenced
this pull request
May 14, 2026
Two related migration-safety fixes:
1. migrateSplitWorkspaceRepos used to commit the DB tx first and
then rename clone dirs — a kill -9 in that window left old
{workspace_repos.id} dirs orphaned and forced a re-clone. Now
the rename runs BEFORE the transaction and an error aborts the
migration (leaves workspace_repos in place so the next run
retries). Counters for renamed / skipped_missing_source /
skipped_target_exists / failed are logged on completion.
2. Add schema_migrations(version, name, applied_at). Open() reads
MAX(version) and skips already-applied migrations. Existing
prod DBs bootstrap by detecting which legacy tables are present.
3. Migration test suite expanded with subtests covering partial
rename, pre-existing target, missing source dir, duplicate
project_path rows, and idempotent re-runs.
Resolves Fix #3, #7, #14.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This was referenced Jun 3, 2026
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.
What
Why
How
Type of change
Checklist
go vet ./...passes (CLI changes)pytest tests/passes (API changes)