Open
Conversation
A bug in used log lib github.com/sirupsen/logrus v1.9.0: Error while reading from Writer: bufio.Scanner: token too long #1370 sirupsen/logrus#1370 That was closing unexpectly the stderr log socket provided by containerpilot to managed services. Good catch by Ema Musella which founds the exact error message that lead us to problem solving. The bug is fixed by updating logrus to release 1.9.3.
Author
|
any news or comment about this fix? Best regards. |
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
1 participant
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.
A bug in used log lib github.com/sirupsen/logrus v1.9.0:
Error while reading from Writer: bufio.Scanner: token too long #1370
sirupsen/logrus#1370
That was closing unexpectly the stderr log socket provided by containerpilot to managed services.
Good catch by Ema Musella which founds the exact error message that lead us to problem solving.
The bug is fixed by updating logrus to release 1.9.3.