You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 25, 2026. It is now read-only.
When starting a local run, there are lots of printouts from both cargo-shuttle and the runtime's startup logic.
A -q / --quiet flag can be added to the run command, that supresses non-error prints in cargo-shuttle. The flag can also be passed on as --quiet to the runtime binary, where it can also be used to supress the lines that are usually printed (the ones that show up with [Runtime] prepended).
A solution that puts the relevant prints inside if-statements should be sufficient.
This issue is open to contribution. Comment if you want to work on it. Feel free to ask for help and guidance here or in our Discord.
Describe the improvement
When starting a local run, there are lots of printouts from both cargo-shuttle and the runtime's startup logic.
A
-q / --quietflag can be added to theruncommand, that supresses non-error prints in cargo-shuttle. The flag can also be passed on as--quietto the runtime binary, where it can also be used to supress the lines that are usually printed (the ones that show up with[Runtime]prepended).A solution that puts the relevant prints inside if-statements should be sufficient.
This issue is open to contribution. Comment if you want to work on it. Feel free to ask for help and guidance here or in our Discord.