Skip to content
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

Rework SyslogLogger to be thread-safe and ensure that loggers don't yield execution #406

Merged
merged 2 commits into from
Jul 27, 2024

Conversation

s-ludwig
Copy link
Member

See #176

@s-ludwig s-ludwig requested a review from l-kramer July 27, 2024 12:09
@s-ludwig s-ludwig force-pushed the issue176_async_logger branch 2 times, most recently from 468ab42 to 1207a05 Compare July 27, 2024 13:26
Uses an asynchronous writer thread to write the log output and avoids any yielding within the thread/task that performs the logging call.

Note that this change breaks the API to create a SyslogLogger instance, but since the previous implementation was so fundamentally broken, we can assume that nobody was using it.
Doing so would break fundamental assumptions about not yielding within low level code that might very well perform logging.
@s-ludwig s-ludwig merged commit b0cf34a into master Jul 27, 2024
12 checks passed
@s-ludwig s-ludwig deleted the issue176_async_logger branch July 27, 2024 14:53
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants