Atm flowkit uses a custom logger that includes a spinner that is deferred. This means that when using flowkit in a service it is not possible to turn on the debug/spinner log since then all output in that service is garbled by this spinner.
Suggest A Solution
Introduce a logging framework like zerolog that is used in many other apps and move the spinner code to flow-cli repo. If needed split up methods that require multipe spinner in cli, but keep the old impl as is for bc.
What are you currently working on that this is blocking?
I am investigating an corner case in flowdiver ingestion engine where crescendo is flaky but the other networks are not. The lack of good observability hurts.
Issue to be solved
Atm flowkit uses a custom logger that includes a spinner that is deferred. This means that when using flowkit in a service it is not possible to turn on the debug/spinner log since then all output in that service is garbled by this spinner.
Suggest A Solution
Introduce a logging framework like zerolog that is used in many other apps and move the spinner code to flow-cli repo. If needed split up methods that require multipe spinner in cli, but keep the old impl as is for bc.
What are you currently working on that this is blocking?
I am investigating an corner case in flowdiver ingestion engine where crescendo is flaky but the other networks are not. The lack of good observability hurts.