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

Rokit does not use stderr for errors properly #17

Closed
filiptibell opened this issue Apr 23, 2024 · 0 comments · Fixed by #14
Closed

Rokit does not use stderr for errors properly #17

filiptibell opened this issue Apr 23, 2024 · 0 comments · Fixed by #14
Assignees
@filiptibell
Labels
bug Something isn't working

Comments

@filiptibell
Copy link
Collaborator

An issue I ran into today on a fresh OS installation:

  1. Ran rokit install, everything looked fine
  2. Ran lune run some-script, which spawned another tool managed by Rokit
  3. The spawned tool fails due to Rokit not being able to run it (rosetta missing), some-script printed out stderr on failure
  4. Nothing was printed, making it difficult to find the root cause of the failure

This would have been easier to diagnose if Rokit printed errors to the proper output stream.
@filiptibell filiptibell mentioned this issue Apr 23, 2024
Merged
@filiptibell filiptibell added the bug Something isn't working label Apr 23, 2024
@filiptibell filiptibell self-assigned this Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@filiptibell filiptibell

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use stderr for tracing output rojo-rbx/rokit
1 participant
@filiptibell