Fix logger watcher race condition #2712
Merged
+29
−23
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.
Previously a backend could be removed from logger and the watcher would not have exited before the
Logger.remove_backend/1
call returned. This meant that a new watcher could not always be started because the child (watcher) might still exist but be about to die.I need to investigate whether switching to a
simple_one_for_one
with non-temporary children that can return:ignore
will cause a problem - it might.