Merge lp:~allenap/maas/dont-crash-when-selecting-fpi--bug-1293676--1.5 into lp:maas/1.5
Proposed by
Gavin Panella
Status: | Merged |
---|---|
Approved by: | Gavin Panella |
Approved revision: | no longer in the source branch. |
Merged at revision: | 2222 |
Proposed branch: | lp:~allenap/maas/dont-crash-when-selecting-fpi--bug-1293676--1.5 |
Merge into: | lp:maas/1.5 |
Diff against target: |
132 lines (+59/-4) 3 files modified
src/maasserver/models/node.py (+4/-4) src/maasserver/node_action.py (+25/-0) src/maasserver/tests/test_node_action.py (+30/-0) |
To merge this branch: | bzr merge lp:~allenap/maas/dont-crash-when-selecting-fpi--bug-1293676--1.5 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jeroen T. Vermeulen (community) | Approve | ||
Review via email: mp+213917@code.launchpad.net |
Commit message
Backport from trunk r2221: Inhibit the controls to change between fast and default installers when the use-fastpath-
To post a comment you must log in.
This looks like a straight backport. Feel free to self-approve those, assuming there are no conflicts.
However I do have a few notes about the code changes that also apply to what's already in trunk. It might be worth addressing them, and then backporting the updated version of the changes:
.
The big warning strings strike me as a bit confusing. Updated? In what way? By whom? Why? These situations often start with the passive voice. Don't do it. The imperative is fine when you're telling the user something they need to do in order to accomplish something — you don't even need to say “please.”
.
Both the ‘inhibit’ methods in node_action.py have this weird indentation:
return dedent("""\ installer tag is defined with an
The use-fastpath-
Did tabs sneak in? I would expect the text inside an argument to the function call to be indented further than the line that starts the function call.
If that makes the indentation too deep for comfortable text flow, why not extract these two identical-looking methods, or parts thereof, into a function outside the classes? In fact, with these two near-identical explanations both repeated, why not extract them into global constants?
Jeroen