Closed andiflabs closed 1 week ago
Running wallet:rescan when not connected to a node produces output like the following:
wallet:rescan
Scanning blocks: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0% | 60 / 624032 | 0.00 / sec | ETA: N/AAdded block seq: 100, hash: 00000...bd9a1 Scanning blocks: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0% | 128 / 624032 | 0.00 / sec | ETA: N/AAdded block seq: 200, hash: 00000...c61b7 Scanning blocks: [░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░] 0% | 282 / 624032 | 0.00 / sec | ETA: N/AAdded block seq: 300, hash: 00000...194db
That is: the progress bar output is disrupted by the scanner logs.
This commit suppresses the logs coming from the wallet so that the progress bar is the only output displayed.
Run yarn start wallet:rescan while a node is NOT running and observe the output.
yarn start wallet:rescan
N/A
Summary
Running
wallet:rescanwhen not connected to a node produces output like the following:That is: the progress bar output is disrupted by the scanner logs.
This commit suppresses the logs coming from the wallet so that the progress bar is the only output displayed.
Testing Plan
Run
yarn start wallet:rescanwhile a node is NOT running and observe the output.Documentation
N/A
Breaking Change
N/A