fix: add pre-action releaseLocks before init-db run #165
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
networkhermit
approved these changes
Jan 10, 2023
arucil
pushed a commit
that referenced
this pull request
Feb 3, 2023
# Why? sometimes init-db run fail because db changelog lock of liquibase # What? cause init-db run waiting timeout # How? add pre-action `releaseLocks` in init-db avoid stuck
wumanho
pushed a commit
to wumanho/apitable
that referenced
this pull request
Feb 6, 2023
# Why? sometimes init-db run fail because db changelog lock of liquibase # What? cause init-db run waiting timeout # How? add pre-action `releaseLocks` in init-db avoid stuck
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.
Why?
sometimes init-db run fail because db changelog lock of liquibase
What?
cause init-db run waiting timeout
How?
add pre-action
releaseLocksin init-db avoid stuck