Open
Conversation
devonestes
force-pushed
the
update-for-new-logger
branch
7 times, most recently
from
01f31db to
187a5d0
Compare
This catches some previously uncaught crash reports that were missed because of the change in pattern in the new logger.
devonestes
force-pushed
the
update-for-new-logger
branch
2 times, most recently
from
a9b7873 to
90cb97b
Compare
devonestes
force-pushed
the
update-for-new-logger
branch
from
90cb97b to
7633d95
Compare
lexmag
force-pushed
the
master
branch
2 times, most recently
from
e3e4210 to
392d43b
Compare
|
For what is worth, #126 (comment). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This catches a previously un-caught crash report that was ignored when using the new Logger.
I also update the CI script to include newer versions of Elixir & Erlang.