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

message.UseBuffer is broken due to a pterm upstream bug #849

Closed
nacx opened this issue Dec 12, 2024 · 0 comments · Fixed by #848
Closed

message.UseBuffer is broken due to a pterm upstream bug #849

nacx opened this issue Dec 12, 2024 · 0 comments · Fixed by #848
Labels
possible-bug Something may not be working triage Awaiting triage from the team

Comments

@nacx
Copy link
Contributor

nacx commented Dec 12, 2024

PR #824 upgraded pterm from v0.12.79 to v0.12.80, and that introduces the pterm bug pterm/pterm#701.
That causes the default writer to not be properly honored by the default writers, breaking the Lula's message.UseBuffer. Instead of being written to the buffer, messages are still written to the default writers (stdout/stderr).

@nacx nacx added the possible-bug Something may not be working label Dec 12, 2024
@github-actions github-actions bot added the triage Awaiting triage from the team label Dec 12, 2024
@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Lula and Friends Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible-bug Something may not be working triage Awaiting triage from the team
Projects
Archived in project
1 participant