--verbose option is incorrectly described in CLI "--help" page #65586

New Issue

Markus Bawidamann · 2019-06-07T04:07:43+02:00

Markus Bawidamann commented

2019-06-07 04:07:43 +02:00

System Information
Operating system: Linux Debian Stretch
Graphics card: Internal/Intel

Blender Version
Broken: (example: 2.80
Blender 2.80 (sub 71)

      build date: 2019-05-22
      build time: 23:51:31
      build commit date: 2019-05-22
      build commit time: 21:50
      build hash: a1ad71304c2d
      build platform: Linux

Not Worked: This was already broken in in 2.79

description:
When using the command line, the --verbose parameter does absolutely nothing, no matter what level I specify.
As described here,
https://blender.stackexchange.com/questions/3049/what-values-do-the-verbose-and-debug-value-options-accept/3063
verbose does not seem to be used in anything else than camera tracking.
The description in the --help page is misleading, it does not says this, so the user assumes that verbose applies to everything. Changing the help page and specifying that it only applies to camera tracking would help users save time by not having to experiment and waste a lot of time, then find the same stack exchange page I did.
I remember running into this years ago and I forgot about it and now it happened again. It would be very quick to just add "The verbose parameter currently only applies to camera tracking"

**System Information** Operating system: Linux Debian Stretch Graphics card: Internal/Intel **Blender Version** Broken: (example: 2.80 Blender 2.80 (sub 71) ``` build date: 2019-05-22 build time: 23:51:31 build commit date: 2019-05-22 build commit time: 21:50 build hash: a1ad71304c2d build platform: Linux ``` Not Worked: This was already broken in in 2.79 description: When using the command line, the --verbose parameter does absolutely nothing, no matter what level I specify. As described here, https://blender.stackexchange.com/questions/3049/what-values-do-the-verbose-and-debug-value-options-accept/3063 verbose does not seem to be used in anything else than camera tracking. The description in the --help page is misleading, it does not says this, so the user assumes that verbose applies to everything. Changing the help page and specifying that it only applies to camera tracking would help users save time by not having to experiment and waste a lot of time, then find the same stack exchange page I did. I remember running into this years ago and I forgot about it and now it happened again. It would be very quick to just add "The verbose parameter currently only applies to camera tracking"

Markus Bawidamann commented

2019-06-07 04:07:43 +02:00

Added subscriber: @MarkusBawidamann-4

Philipp Oeser commented

2019-06-07 10:42:54 +02:00

Added subscribers: @brecht, @lichtwerk

Philipp Oeser commented

2019-06-07 10:42:54 +02:00

Not sure if this could be considered a bug.

Perhaps this could be made clearer by stating this is for libmv only, also the value you set might be better called "level"
P996: T65586_snippet



diff --git a/source/creator/creator_args.c b/source/creator/creator_args.c
index fe7f9c52f4d..29289b0cf1d 100644
--- a/source/creator/creator_args.c
+++ b/source/creator/creator_args.c
@@ -1417,8 +1417,8 @@ static int arg_handle_threads_set(int argc, const char **argv, void *UNUSED(data
 }
 
 static const char arg_handle_verbosity_set_doc[] =
-    "<verbose>\n"
-    "\tSet logging verbosity level.";
+    "<level>\n"
+    "\tSet logging verbosity level. (libmv only atm)";
 static int arg_handle_verbosity_set(int argc, const char **argv, void *UNUSED(data))
 {
   const char *arg_id = "--verbose";

@brecht: this also seems to be used for cycles logging (if WITH_CYCLES_LOGGING is ON -- though this does not seem to have an effect, maybe I am using it wrong though...)?

Not sure if this could be considered a bug. Perhaps this could be made clearer by stating this is for libmv only, also the value you set might be better called "level" [P996: T65586_snippet](https://archive.blender.org/developer/P996.txt) ``` diff --git a/source/creator/creator_args.c b/source/creator/creator_args.c index fe7f9c52f4d..29289b0cf1d 100644 --- a/source/creator/creator_args.c +++ b/source/creator/creator_args.c @@ -1417,8 +1417,8 @@ static int arg_handle_threads_set(int argc, const char **argv, void *UNUSED(data } static const char arg_handle_verbosity_set_doc[] = - "<verbose>\n" - "\tSet logging verbosity level."; + "<level>\n" + "\tSet logging verbosity level. (libmv only atm)"; static int arg_handle_verbosity_set(int argc, const char **argv, void *UNUSED(data)) { const char *arg_id = "--verbose"; ``` @brecht: this also seems to be used for cycles logging (if WITH_CYCLES_LOGGING is ON -- though this does not seem to have an effect, maybe I am using it wrong though...)?

Brecht Van Lommel was assigned by Sebastian Parborg

2019-06-14 11:41:08 +02:00

Brecht Van Lommel removed their assignment 2019-06-14 11:46:14 +02:00

Sergey Sharybin was assigned by Brecht Van Lommel

2019-06-14 11:46:14 +02:00

Sergey Sharybin commented

2019-06-14 12:05:56 +02:00

This isn't Libmv only. everything what depends on Glog will be affected. This includes Ceres, Cycles, Libmv. Keep in mind, Ceres is not only used by Libmv.

I also don't find it a bug that --verbose by itself does nothing. There are so many areas in Blender, that would simply bloat the output. You need to use --debug-FOO to enable logging in that area, and then within that area (if it supports that).

This isn't Libmv only. everything what depends on Glog will be affected. This includes Ceres, Cycles, Libmv. Keep in mind, Ceres is not only used by Libmv. I also don't find it a bug that `--verbose` by itself does nothing. There are so many areas in Blender, that would simply bloat the output. You need to use `--debug-FOO` to enable logging in that area, and then within that area (if it supports that).

Sergey Sharybin commented

2019-06-28 15:49:49 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2019-06-28 15:49:49 +02:00

Sergey Sharybin commented

2019-06-28 15:49:49 +02:00

Committed fixes at 0511de99bb and e8cb477f8a, so hopefully everything works correct,m according to the design and is clear for usage.

Thanks for the report.

Committed fixes at 0511de99bb and e8cb477f8a, so hopefully everything works correct,m according to the design and is clear for usage. Thanks for the report.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

--verbose option is incorrectly described in CLI "--help" page #65586