chore(raiko-lib): auto logging

[35359595]

• automatic logging if RUST_LOG env not present is set to info level;
• println logs replaced with tracing::debug;
• logging levels demoted to debug on most chatty outputs;
• install script sources sp1 not only on CI but also if not found in current $PATH;

[dantaik]

you have to fix your PR title first, something like "chore(project_name): verb ..."

[Brechtpd]

Some good changes!

But feels like info now prints very little, and debug prints so much stuff it's hard to find anything back, so I think we need to tweak things some more so that the default log level still prints out a sufficient amount of useful information. Also seems like

raiko/lib/src/builder/execute.rs

Line 286 in a1ee3ae

debug!(" Ok: {result:?}");

needs to changed to trace level now if we want to use the debug level more because that one is very spammy and normally not useful.

I think it's okay to print some stuff using println for stuff that is mostly just important while you're waiting on the block, like the transaction progress or the data fetching progress. That stuff is not so important for the logs, but very useful while you're staring at it and wondering how long something will still take to finish.

Currently the block execution though is very messy because of the optimistic execution still printing a lot of stuff, I think to solve that we could not print/log anything when is_optimistic is true in execute_transactions. Or something like that. We could also have a custom logger trait that people could set but that seems overkill.

[petarvujovic98]

Good stuff here @35359595. Some of the println usage for progress/waiting feedback could get hidden behind a #[cfg(debug_assertions] so it's only visible when running in dev mode (e.g. people looking at the screen for progress), not suitable for tracing as that data doesn't help with either metrics or debugging after the fact.a

[johntaiko]

How is the progress going here?

It has some negative impacts on our production environment, and we hope it can be resolved ASAP :)