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
What is the purpose of --processed option nowadays? It used to output the big picture in the requested format; v1.2.0 outputs a Python bytes literal which IMHO makes no sense. Please see below:
$ ./git-big-picture-v0.9.0 --format=svg -pVO | xmllint -noout -
$ git big-picture --format=svg -pVO | xmllint -noout -
-:1: parser error : Start tag expected, '<' not found
b'<?xml version="1.0" encoding="UTF-8" standalone="no"?>\n<!DOCTYPE svg PUBLIC "
^
I found the old behavior useful and sane.
Br. Sami
The text was updated successfully, but these errors were encountered:
Hi @oCCtet , thanks for bringing this to attention. I confirm this behavior as a bug. My guess is that it's a regression from the migration to Python 3. I'm optimistic this can be fixed shortly.
Please note that use of versions <1.0.0 is not advised today because these are vulnerable to security issue CVE-2021-3028. (In case that was your plan for a workaround while waiting for the fix.)
hartwork
changed the title
The --processed output is suspicious (or outright broken?)
[>=0.10.0] Argument --processed stopped producing healthy output
Mar 21, 2022
What is the purpose of --processed option nowadays? It used to output the big picture in the requested format; v1.2.0 outputs a Python bytes literal which IMHO makes no sense. Please see below:
I found the old behavior useful and sane.
Br. Sami
The text was updated successfully, but these errors were encountered: