-
-
Notifications
You must be signed in to change notification settings - Fork 510
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: don't panic when logs waits for more than 5 seconds #1777
Closed
Closed
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
ada9d42
fix: synchronize consumer in tests
martin-sucha 075b0f3
fix: don't panic when logs waits for more than 5 seconds
martin-sucha 8b68f2a
Merge branch 'main' into ms/issue-946-v2
martin-sucha 0b6d915
Add a comment explaining synchronization
martin-sucha bc8715e
Handle errors in log producer gracefully
martin-sucha eab0920
Merge branch 'main' into ms/issue-946-v2
mdelapenya 57f6569
Merge branch 'main' into ms/issue-946-v2
mdelapenya 1cdb8ce
chore: use time.After instead of sleep
mdelapenya 9e4b5a1
chore: print logs honouring context cancellation
mdelapenya aec5067
Merge branch 'main' into ms/issue-946-v2
mdelapenya 7453e4a
chore: merge context done conditions
mdelapenya e143444
chore: remove context cancelation checks, as the error comes from an …
mdelapenya 8c9fbd3
chore: remove context cancelation checks, as the error comes from an …
mdelapenya 51d6f8b
chore: simplify print
mdelapenya File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we panicking here? If you just want to log the error and return then isn't it better to consistently do it in the same way?
If the purpose is to print the stack trace then maybe panic is best, but why here?