brotli --test --verbose should show a message #264

New Issue

claunia · 2026-01-29T20:41:05Z

claunia commented

2026-01-29 20:41:05 +00:00

Originally created by @stokito on GitHub (Oct 29, 2018).

When running a integrity test brotli shows nothing and t his is correct according to unix philosophy.
But when I asked the brotli to be verbose it still didn't show anything:

$ brotli -vt goodarchive.br
$ brotli -vt corrupt.br
corrupt input [corrupt.br]

What do I expect is the same behavior as for gzip, xz and many other compressors:

$ gzip -vt goodarchive.gz
goodarchive.gz:	 OK
$ gzip -vt corrupt.br
gzip: corrupt.gz: not in gzip format

As you can see in verbose mode test shows a file name and status OK.

Could you make brotli to work similar with other compressors?

Originally created by @stokito on GitHub (Oct 29, 2018). When running a integrity test brotli shows nothing and t his is correct according to unix philosophy. But when I asked the brotli to be verbose it still didn't show anything: ``` $ brotli -vt goodarchive.br $ brotli -vt corrupt.br corrupt input [corrupt.br] ``` What do I expect is the same behavior as for `gzip`, `xz` and many other compressors: ``` $ gzip -vt goodarchive.gz goodarchive.gz: OK $ gzip -vt corrupt.br gzip: corrupt.gz: not in gzip format ``` As you can see in verbose mode test shows a file name and status OK. Could you make brotli to work similar with other compressors?

claunia closed this issue

2026-01-29 20:41:05 +00:00

claunia commented

2026-01-29 20:41:05 +00:00

@eustas commented on GitHub (Oct 29, 2018):

Surely. Will implement that soon (when get some free cycles =)

@eustas commented on GitHub (Oct 29, 2018): Surely. Will implement that soon (when get some free cycles =)

claunia commented

2026-01-29 20:41:06 +00:00

@stokito commented on GitHub (Oct 30, 2018):

@eustas thank you. Also please note that gzip, uncompress, bzip2, lzip, lzma, xz, lzop compressors usually prints an output to stderr instead of stdout but rar and 7zip prints to stdout.
So I'm not sure what is a correct behavior but please implement according to some standard de-facto i.e. stderr.

@stokito commented on GitHub (Oct 30, 2018): @eustas thank you. Also please note that gzip, uncompress, bzip2, lzip, lzma, xz, lzop compressors usually prints an output to `stderr` instead of `stdout` but `rar` and `7zip` prints to `stdout`. So I'm not sure what is a correct behavior but please implement according to some standard de-facto i.e. stderr.

claunia commented

2026-01-29 20:41:06 +00:00

@eustas commented on GitHub (Oct 30, 2018):

Currently CLI prints something to stdout only for --help and --version, i.e. when user directly requested some output.
For "verbose" + "test" options stderr seems to be the only right destination, to make it consistent with other "verbose" outputs.

@eustas commented on GitHub (Oct 30, 2018): Currently CLI prints something to `stdout` only for `--help` and `--version`, i.e. when user directly requested some output. For "verbose" + "test" options `stderr` seems to be the only right destination, to make it consistent with other "verbose" outputs.

claunia commented

2026-01-29 20:41:07 +00:00

@eustas commented on GitHub (Dec 15, 2021):

I think it is fixed now:

 ~$ brotli -tv gato.html.br 
Decompressed [gato.html.br]: 698 B -> 4.395 KiB

@eustas commented on GitHub (Dec 15, 2021): I think it is fixed now: ``` ~$ brotli -tv gato.html.br Decompressed [gato.html.br]: 698 B -> 4.395 KiB ```

claunia referenced this issue

2026-01-29 20:51:17 +00:00

[PR #265] [CLOSED] Avoid integer overflow on x86_64-mingw, closes #264 #864

claunia referenced this issue

2026-01-29 20:51:19 +00:00

[PR #265] Avoid integer overflow on x86_64-mingw, closes #264 #869

Sign in to join this conversation.