discussion: --verbose flag

[0xSage]

Problem

Sometimes we want verbose logging when running commands

Questions

1. Do users have to run --verbose for every command?
2. Or is --verbose a toggle that turns on/off a verbosity setting?
3. What is the intended UX of --verbose?
4. Verbose will emit all of the logs that would otherwise write into /logs?

The current verbose stdout is quite hard to understand:

❯ sudo cortex-nightly --verbose
20240919 09:50:09.396980 UTC 3420791 INFO  Engine release path: https://delta.jan.ai/cortex/latest/version.json - cortex_upd_cmd.h:56
❯ sudo cortex-nightly --verbose engines list
20240919 09:50:25.655993 UTC 3420941 INFO  Config file name: .cortexrc-nightly - file_manager_utils.h:105
+---+--------------+-------------------+---------+--------------+
| # | Name         | Supported Formats | Version | Status       |
+---+--------------+-------------------+---------+--------------+
| 1 | ONNXRuntime  | ONNX              | 0.0.1   | Incompatible |
+---+--------------+-------------------+---------+--------------+
| 2 | llama.cpp    | GGUF              | 0.0.1   | Ready        |
+---+--------------+-------------------+---------+--------------+
| 3 | TensorRT-LLM | TensorRT Engines  | 0.0.1   | Incompatible |
+---+--------------+-------------------+---------+--------------+
20240919 09:50:25.660971 UTC 3420941 INFO  Engine release path: https://delta.jan.ai/cortex/latest/version.json - cortex_upd_cmd.h:56

[vansangpfiev]

1. Do users have to run --verbose for every command?
2. Or is --verbose a toggle that turns on/off a verbosity setting?
   We have to run --verbose for each command. We don't save any state for CLI, so I think it does not make sense to turns on/off setting
3. What is the intended UX of --verbose?
4. Verbose will emit all of the logs that would otherwise write into /logs?
   The --verbose print all the LOG_INFO into the terminal, that will help user/dev to have more information when running a command

[0xSage]

1. Do users have to run --verbose for every command?
2. Or is --verbose a toggle that turns on/off a verbosity setting?
   We have to run --verbose for each command. We don't save any state for CLI, so I think it does not make sense to turns on/off setting
3. What is the intended UX of --verbose?
4. Verbose will emit all of the logs that would otherwise write into /logs?
   The --verbose print all the LOG_INFO into the terminal, that will help user/dev to have more information when running a command

Is is just LOG_INFO? Or will it emit all levels of logs.

[dan-homebrew]

@0xSage I think --verbose is fairly standard across CLIs.

• I think we should structure discussion around specific commands' --verbose
• I don't think verbose is a setting
• I would handle this later, after the basic stuff has been roughed in