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

Fix race condition in log monitoring #982

Merged
merged 1 commit into from
Feb 5, 2024

Conversation

jonjohnsonjr
Copy link
Contributor

For some reason we were using os.Pipe instead of io.Pipe for an in-process pipe. I've switched those over to using io.Pipe so we can CloseWithError.

Also, switched to using errgroup.Group instead of manual channel signaling.

Now, when we hit an error, we actually log that error instead of the line just before that error.

imjasonh
imjasonh previously approved these changes Feb 5, 2024
Copy link
Member

@imjasonh imjasonh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️

For some reason we were using os.Pipe instead of io.Pipe for an
in-process pipe. I've switched those over to using io.Pipe so we can
CloseWithError.

Also, switched to using errgroup.Group instead of manual channel
signaling.

Now, when we hit an error, we actually log that error instead of the
line just before that error.

Signed-off-by: Jon Johnson <jon.johnson@chainguard.dev>
@jonjohnsonjr jonjohnsonjr merged commit 4aeb670 into chainguard-dev:main Feb 5, 2024
32 checks passed
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.

3 participants