Don't fail completely when PowerManager.init/1 raises #259
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When
PowerManager.init/1
implementations fail, supervision restartsGenServers like expected. However,
init/1
really isn't supposed tofail and when it does, it has the effect of propogating failures all the
way up which eventually takes down VintageNet. While this is almost
certainly a programming error, the result is particularly harsh.
To better support debugging this issue, this commit logs the error and
disables the power manager.
The downside to this is that if there's a transient that would have been
fixed by a restart, that no longer happens and perhaps the network won't
work. While this isn't good, devices that require network connections
to function need to have a "watchdog" that verifies that there's a
network connection anyway. That logic should catch this.