A lot of noisy message: Updated the logging layer according to log_config.json`

[mrLSD]

It is a lot of noisy log messages in the output:

Updated the logging layer according to `log_config.json`

Link to GitHub CI:
https://github.com/aurora-is-near/aurora-workspace/actions/runs/4893433957/jobs/8736389991#step:5:473

no-capture flag is not enabled.

Tested in 3 completely different projects. Same log message is in the output.

[itegulov]

Seems like this is happening because of near/nearcore#8810. Not sure if there is a good way to silence this other than just not inheriting stdout from sandbox. @ChaoticTempest thoughts?

[ChaoticTempest]

yeah looks like we're just inheriting stdout by default for sandbox processes. A couple options we have for silencing it:

• set the sandbox proccess stdout to Stdio::null which just directs it to /dev/null, but nearcore might have informative stdout/stderr related info if it crashes or something can be added in the future, so probably not the best option.
• Since we have sandbox/network-builders now, we can have an extra parameter there saying whether or not to include stdout, with the default being not to include

[itsyaasir]

👋🏾 As per our discussion with @frol , I would like to take up this issue. Thanks

[frol]

Another option I would consider - fix it on nearcore side - avoid using println (use logging instead)

[itsyaasir]

Another option I would consider - fix it on nearcore side - avoid using println (use logging instead)

Yeah, I think I will look into this.

[itsyaasir]

I have confirmed that the messages are no longer printed in the stdout. Attached is a screenshot with two commands.

• The first command is running with custom sandbox built against this branch, as you can see there's no println messages
• The second command is using the default sandbox and the print messages are there

PS:- The default version uses Commit hash for the sandbox "versioning", we will have to update the hash if we want to use the new sandbox which doesn't have the logging messages.

[mrLSD]

@itsyaasir is there a way to test it with workspaces-rs? Maybe git hash?

P.F. Out of discussion: what's the cool plugin for zsh? ))

[itsyaasir]

@itsyaasir is there a way to test it with workspaces-rs? Maybe git hash?

P.F. Out of discussion: what's the cool plugin for zsh? ))

Unfortunately I don't have git hash, I can provide the sandbox that I used which I built it based on this PR. To get this changes in the workspace-rs, we need the PR merged and update the near-sandbox-utils to use the newer sandbox (from what I have seen). Correct me if am wrong

PS: It's not zsh plugin, I am using starship-rs shell which has this nice simple preset and some customized icons.

[itsyaasir]

This issue can be closed, altho we will need to update the sandbox utils crate to use the latest near sandbox.

[frol]

Resolved in near/nearcore#9277

[mrLSD]

The issue is still online. NEAR Issue was resolved, but we're still have same issue using workspace-rs. Any advice, please?
@frol @itsyaasir

[ghost]

@mrLSD The main reason it is showing now is because workspace-rs is using an older sandbox, this PR should get rid of the logging texts.