fix: do not reuse Base class on alembic migration script
#3254
Conversation
This file contains 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
github-actions
bot
added
comp:manager
lablup-octodog
pushed a commit
that referenced
this pull request
Dec 16, 2024
Backported-from: main (24.12) Backported-to: 24.09 Backport-of: 3254
github-merge-queue bot
pushed a commit
that referenced
this pull request
Dec 16, 2024
…3255) Co-authored-by: Kyujin Cho <[email protected]>
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.
Table definition on alembic migration script should remain independently and should not be affected by the definitions declared at
ai.backend.manager.modelspackage. This update alters existing database migration script but won't change the schema itself, so existing users do not have to take extra steps.Checklist: (if applicable)