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.

Sign up for GitHub

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

Jump to bottom

fix: should we always be tracking component stderr? #490

Open
starpit opened this issue Oct 30, 2024 · 0 comments
Open

fix: should we always be tracking component stderr? #490

starpit opened this issue Oct 30, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@starpit
Copy link
Member

starpit commented Oct 30, 2024

Right now, the minio and workstealer components may fail silently. We should be tracking (via pkg/boot.watchLogs() the stderr of all components?

Also right now, backend.streamer.ComponentLogs() does not allow distinguishing stdout from stderr. In Kubernetes there is no distinction... in local there is.
@starpit starpit added the bug Something isn't working label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@starpit