-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clean up old TxParameters SQL table #1735
Conversation
-- | This table became @protocol_parameters@. | ||
removeOldTxParametersTable :: Sqlite.Connection -> IO () | ||
removeOldTxParametersTable conn = do | ||
dropTable <- Sqlite.prepare conn "DROP TABLE IF EXISTS tx_parameters;" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could be nice to first look for the table using isFieldPresent
and then, log accordingly depending on the outcome?
bors r+ |
1735: Clean up old TxParameters SQL table r=KtorZ a=rvl ### Issue Number Closes #1727 ### Overview Remove an old SQL table, if it exists. Co-authored-by: Rodney Lorrimar <[email protected]>
Build failed |
2fa5f70
to
20ef4ff
Compare
bors r+ |
From the buildkite log it looks like the integration tests may have a fd leak. |
1735: Clean up old TxParameters SQL table r=KtorZ a=rvl ### Issue Number Closes #1727 ### Overview Remove an old SQL table, if it exists. Co-authored-by: Rodney Lorrimar <[email protected]>
@rvl Yes, I've observed this a few times already and I am trying to pinpoint the issue without success. Sometimes, there's something causing an internal error on the server, after what, workers stop being removed and simply pile up as the test move forward. Listing wallets returns a bazillion number of wallets while also causing all subsequent test to fail. The cause is unclear. |
Build failed |
b33273e
to
b263454
Compare
bors r+ |
Build succeeded |
Issue Number
Closes #1727
Overview
Remove an old SQL table, if it exists.