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
When checking the help menu (usage) of mithril-client it states each additional v increases verbosity from WARNING, to INFO to DEBUG. However, in practice, it appears a single v produces INFO and two v's produce DEBUG level.
Mithril client is from release binaries 2337.0 - mithril-client 0.4.2+7d5a683.
When running mithril-client -vv [...] the following can be observed:
Oct 30 16:01:49.508 DEBG Run Mode: dev
Oct 30 16:01:49.508 DEBG Reading configuration file './config/dev.json'.
Oct 30 16:01:49.508 DEBG New AggregatorHTTPClient created
Oct 30 16:01:49.508 DEBG New MithrilCertificateVerifier created
Oct 30 16:01:49.508 DEBG Snapshot service: show.
Oct 30 16:01:49.508 DEBG Snapshot service: list.
Oct 30 16:01:49.508 DEBG GET url='https://aggregator.release-preprod.api.mithril.network/aggregator/artifact/snapshots'.
Oct 30 16:01:49.526 DEBG Prepare request with version: 0.1.11
Oct 30 16:01:50.427 DEBG GET url='https://aggregator.release-preprod.api.mithril.network/aggregator/artifact/snapshot/e9e0172b9b916e5a5432fac75f7187ba20c50426d70ed900e22a53aa7304b804'.
Oct 30 16:01:50.451 DEBG Prepare request with version: 0.1.11
1/6 - Checking local disk info…
Oct 30 16:01:51.220 DEBG Snapshot service: download.
2/6 - Fetching the certificate's information…
Oct 30 16:01:51.221 DEBG GET url='https://aggregator.release-preprod.api.mithril.network/aggregator/certificate/9a7718437af171c64adc8ebd93e1de78996c27a39e1cf3a782189c90afe9f841'.
Oct 30 16:01:51.235 DEBG Prepare request with version: 0.1.11
3/6 - Verifying the certificate chain…
⠁
Oct 30 16:01:52.682 DEBG Verifying certificate, certificate_beacon: Beacon { network: "preprod", epoch: Epoch(103), immutable_file_number: 1987 }, certificate_previous_hash: a5cb43ffd7989e8a03235cedb7a30cd9b5c8e
fcbbabc0e5510b514187308b732, certificate_hash: 9a7718437af171c64adc8ebd93e1de78996c27a39e1cf3a782189c90afe9f841
I'm unsure if the typo of DEBG vs. DEBUG is intentional and all logs are using a 4-character log level, I have not seen if it's WARN or WARNING in the logs. If it is not being limited to 4 characters then DEBG I presume is also a typo.
Expected behavior
Using one v would enable WARNING and two V's would enable both WARNING and INFO levels, but not the DEBUG level.
The text was updated successfully, but these errors were encountered:
Context & versions
When checking the help menu (usage) of mithril-client it states each additional
v
increases verbosity from WARNING, to INFO to DEBUG. However, in practice, it appears a single v produces INFO and two v's produce DEBUG level.Mithril client is from release binaries 2337.0 - mithril-client 0.4.2+7d5a683.
Steps to reproduce
mithril-client -h
Verbosity level (-v=warning, -vv=info, -vvv=debug)
mithril-client -v [...]
mithril-client -vv [...]
Actual behavior
When running
mithril-client -vv [...]
the following can be observed:I'm unsure if the typo of DEBG vs. DEBUG is intentional and all logs are using a 4-character log level, I have not seen if it's WARN or WARNING in the logs. If it is not being limited to 4 characters then DEBG I presume is also a typo.
Expected behavior
Using one v would enable WARNING and two V's would enable both WARNING and INFO levels, but not the DEBUG level.
The text was updated successfully, but these errors were encountered: