resticity
resticity copied to clipboard
ad-on-is
"Error: invalid character ',' looking for beginning of object key string" when trying to browse a snapshot on a remote repo
When I click on the yellow path in the snapshot view, it tries to load something, but then fails with the message from the title.
The repo is set up on a sftp server running EndeavourOS (basically Arch).
I'm running resticity 1.0.46-1 (aur version) on CachyOS on the client side.
I followed the repo initialization steps in the restic documentation
Here is a screenshot from the snapshot whose path I want to browse...
...and from it not working
I really appreciate any information on how/whether this is fixable by me or if I just have to wait for some future update.
Thanks in advance.
EDIT: In the logs it gives me the following error message:
FetchError: [POST] "http://localhost:11278/api/repositories/58c1b1c0-2346-4835-a921-f43baa13b472/snapshots/e51958c9c2877a28da51bbcf7a852afe2cd9898585c0f3b98eb5d28f5885cebe/browse": 500 Internal Server Error
Sorry for the delayed answer... I was on vacation. I haven't worked on the project for a while now, so there haven't been any "breaking changes" ever since.
What version of restic are you using? Maybe they changed something there. All resticity does, is, it uses restic commands with the --json attribute and parses the json output.
Would you mind testing restic -r /path/to/repo ls latest
The above command indeed works and I can see the list of files that I have backed up.
I'm using Restic version 0.17.0-1, which was automatically installed as a dependency.
Ok, so I downloaded Restic 0.16.5 and it's working, so I'm guessing something changed in the 0.17 version that broke Resticity. They do have a long list of changes.
Hi there, I'm sorry for the late answer. I was on vacation without access to my laptop for a week. I can confirm that downgrading the restic package to 0.16.5-1 solves the problem I've been having. I'll close this issue now. Edit: Thanks for the help btw...
Shouldn't it be fixed with the latest version instead? With the amount of changes and bug fixes, it seems to be a better option than simply downgrading.
@QuarkZ26 I totally agree here.
tbf, I mostly run It in a Docker and it serves my purpose without issues.
And, tbh... the current state of packaging on Linux, especially Flatpak (Flathub) in combination with electron-like-apps is a mess, which keeps me less motivated to work on it.
still getting this error on Arch. Can you fix for latest version please?
