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

Use read_line instead of next_line in stderr #325

Merged
merged 5 commits into from
Jul 26, 2023

Conversation

haixuanTao
Copy link
Collaborator

By using read_line, we make stderr behave similarly to stdout.

stderr that use next_line use to not add newline at the end of each line which made me open #320.
This made stdout that use read_line have two newlines. This was introduced here: #300

This PR fix this issue.

Moreover, I have added functionality in the stderr thread to retrieve python traceback and output it as one block in the DEBUG traces but also push it as an ERROR trace in daemon so that user don't have to check log file.

This is done by replicating the functionality in stdout in stderr and retrieve the full traceback for python nodes.

By using read_line, we make stderr similar to stdout.

Moreover, we can replicate the functionality in stdout in stderr and retrieve
the full traceback for python nodes. This way, we can print python errors in the daemon logs
without having to look at the log files.
By using cargo instead of git, we make compilation not have to git clone
dora project.
@haixuanTao haixuanTao requested a review from phil-opp July 26, 2023 13:34
…late

Use cargo instead of git in Rust `Cargo.toml` template
@phil-opp phil-opp enabled auto-merge July 26, 2023 13:43
@phil-opp phil-opp merged commit 89bae20 into main Jul 26, 2023
28 checks passed
@phil-opp phil-opp deleted the fix-uneven-newline-stderr-stdout branch July 26, 2023 14:21
@haixuanTao haixuanTao mentioned this pull request Sep 6, 2023
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