-
Notifications
You must be signed in to change notification settings - Fork 81
[IMP] modules: skip autoinstall of unintalled modules #367
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
base: master
Are you sure you want to change the base?
[IMP] modules: skip autoinstall of unintalled modules #367
Conversation
|
upgradeci retry with only base iap_mail |
aec1a38 to
7464dda
Compare
|
upgradeci retry with always only base iap_mail |
7464dda to
4c2b786
Compare
aj-fuentes
left a comment
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.
A first quick pass, some nits to keep the diff to the point :)
I will experiment with this a bit soon. Thanks!
4c2b786 to
64feb35
Compare
64feb35 to
888f583
Compare
| _assert_modules_exists(cr, module) | ||
| to_autoinstall = _get_autoinstallable_modules(cr, module) | ||
| if to_autoinstall: | ||
| if module in ENVIRON["__modules_to_skip_autoinstall"]: |
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.
This at the moment is not doing anything because the method trigger_auto_install is only called in the context of new_module and in some pre scripts also for new modules. But it does not hurt to keep it just in case, as the method can be called elsewhere
888f583 to
005e6a3
Compare
src/util/modules.py
Outdated
| "Skipping the auto installation of module %r despite having all its auto install dependencies installed " | ||
| "by the force install of %r, because it was previously uninstalled." |
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.
We should make this more direct:
| "Skipping the auto installation of module %r despite having all its auto install dependencies installed " | |
| "by the force install of %r, because it was previously uninstalled." | |
| "Module %r won't be auto installed because its original dependencies were already installed. " | |
| "Yet all its auto install dependencies were installed by the force install of {!r}." |
- First we tell what we skip and why: no module installed
- Then we we tell how we reached this point: as a result of an install of another module.
Both details are highly useful when debugging auto-install issues.
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.
updated, still not the smoothest sentence but it's for our own info anyway
In the case where an autoninstall module is uninstalled by users prior to the upgrade start, this module could be reinstalled during the upgrade if there were dependency changes and those dependencies get force installed. This improvement keeps track of any module that was elligible for autoinstall before the upgrade starts and skips its force installation when dependencies change.
005e6a3 to
f319738
Compare

In the case where an autoninstall module is uninstalled by users prior to the upgrade start, this module could be reinstalled during the upgrade if there were dependency changes and those dependencies get force installed. This improvement keeps track of any module that was illegible for autoinstall before the upgrade starts and skips its force installation when dependencies change.