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

sys_log: write to stdout #1115

Merged
merged 4 commits into from
Nov 7, 2023
Merged

sys_log: write to stdout #1115

merged 4 commits into from
Nov 7, 2023

Conversation

SchmErik
Copy link
Contributor

@SchmErik SchmErik commented Nov 7, 2023

Previously, sys_log printed the message via println!. This change writes sys_log to whatever stdout is pointing to so that the output can be captured in the same manner in as how user specifies stdout to be handled.

Closes: #1028

Previously, sys_log printed the message via println!. This change writes
sys_log to whatever stdout is pointing to so that the output can be captured in
the same manner in as how user specifies stdout to be handled.
Copy link

vercel bot commented Nov 7, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
website ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 7, 2023 6:14pm

@flaub flaub added this to the 0.19.1 milestone Nov 7, 2023
@flaub flaub enabled auto-merge (squash) November 7, 2023 07:42
@flaub flaub disabled auto-merge November 7, 2023 08:20
@flaub flaub merged commit cd1b914 into main Nov 7, 2023
22 checks passed
@flaub flaub deleted the erik/log-to-stdout branch November 7, 2023 20:23
flaub added a commit that referenced this pull request Nov 8, 2023
Previously, sys_log printed the message via println!. This change writes
sys_log to whatever stdout is pointing to so that the output can be
captured in the same manner in as how user specifies stdout to be
handled.

Closes: #1028

---------

Co-authored-by: Frank Laub <flaub@risc0.com>
flaub added a commit that referenced this pull request Nov 8, 2023
Previously, sys_log printed the message via println!. This change writes
sys_log to whatever stdout is pointing to so that the output can be
captured in the same manner in as how user specifies stdout to be
handled.

Closes: #1028

---------

Co-authored-by: Frank Laub <flaub@risc0.com>
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.

Allow env::log to be captured and exposed via ExecutorEnv
2 participants