-
Notifications
You must be signed in to change notification settings - Fork 37
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 colocated db preparation bug when using JsrunSettings
#339
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #339 +/- ##
===========================================
+ Coverage 87.17% 87.19% +0.02%
===========================================
Files 59 59
Lines 3531 3531
===========================================
+ Hits 3078 3079 +1
+ Misses 453 452 -1
|
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.
Good catch! LGTM, pending one change to the changelog
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.
One small question, but otherwise my approval stands!
A model fails to properly configure colocated db settings when the run settings are of type
JsrunSettings.
This bug was introduced when protected members were made public (due to linter noting public use) but the change was partially rolled back.The model method
_set_colocated_db_settings
attempts the following:There are no run settings classes with an attribute of that name.
JsrunSettings
does have_prep_colocated_db
(note protected/underscore).This change fixes the incorrect call to a non-existent method by invoking
self.run_settings._prep_colocated_db(...)
instead.