-
Notifications
You must be signed in to change notification settings - Fork 20
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
Fix sqlite3 remote_resource_uuid update #249
Conversation
890f00c
to
bff7dbe
Compare
Codecov Report
@@ Coverage Diff @@
## master #249 +/- ##
=======================================
Coverage 99.34% 99.34%
=======================================
Files 54 54
Lines 2145 2145
=======================================
Hits 2131 2131
Misses 14 14
Continue to review full report at Codecov.
|
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.
As discussed offline, I'm fine with the changes.
Found only a minor typo, feel free to fix it or not.
docs/source/changes/249_fix_sqlite_registry_remote_uuid_update.yaml
Outdated
Show resolved
Hide resolved
….yaml Co-authored-by: Max Fischer <maxfischer2781@gmail.com>
Thanks a lot, I fixed it. |
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.
Looks fine and straight forward 👍
Introducing #247 revealed a bug in TARDIS. The
remote_resource_uuid
in theSqliteRegistry
plugin in not updated at all. As a result, TARDIS keeps crashing on restarts due to the missingremote_resource_uuid
until the DB has been removed.This pull request add the missing
remote_resource_uuid
attribute to the update database calls and fixes #248.