Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

restic json output invalid #2281

Closed
mpetrazzo opened this issue May 21, 2019 · 1 comment · Fixed by #2285
Closed

restic json output invalid #2281

mpetrazzo opened this issue May 21, 2019 · 1 comment · Fixed by #2285

Comments

@mpetrazzo
Copy link

Output of restic version

restic 0.9.4 compiled with go1.12.1 on linux/amd64

How did you run restic exactly?

restic -r s3:http://minioip:9000/bucket --json find * -s id | jq .

What backend/server/service did you use to store the repository?

s3

Expected behavior

jq read restic json output correctly

Actual behavior

jq return me an error:
parse error: Invalid numeric literal at line 1, column 657818146

Steps to reproduce the behavior

On windows system, create a file called randomfilename.%202018 and after run restic backup
After the backup, run find command and export the output in json format. You'll see that it's malformed:
[cut]
"path":"/path/randomfilename.%!"(MISSING),"permissions":"-rw-rw-rw-",...
[cut]

Do you have any idea what may have caused this?

no

Do you have an idea how to solve the issue?

no

Did restic help you or made you happy in any way?

tooooo much!
thanks for this very useful tool!

@mholt
Copy link
Contributor

mholt commented May 21, 2019

Probably we are using Printf when we should be using Println instead.

curiousleo added a commit to curiousleo/restic that referenced this issue May 26, 2019
curiousleo added a commit to curiousleo/restic that referenced this issue May 26, 2019
rawtaz pushed a commit to curiousleo/restic that referenced this issue Feb 14, 2020
rawtaz pushed a commit to curiousleo/restic that referenced this issue Feb 15, 2020
seqizz pushed a commit to seqizz/restic that referenced this issue May 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants