-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Garbage collection error: Unexpected data after root element - follow up to #13554 #14355
Comments
@spylogsster @bbondy given this error blocks the feature (and us, from testing) in #13554, should we take a look at this soon-ish? Thanks! |
@lidel we got wrong formatted json from ipfs node like:
|
@brave/legacy_qa when retesting this the steps from #13554 (comment) can also be used. However, per @spylogsster in #13554 (comment) we should visit additional sites to increase storage usage prior to running garbage collection. |
One can browse @spylogsster I believe the streaming response is valid (we use newline-delimited JSON (NDJSON) notation), it is our docs at https://docs.ipfs.io/reference/http/api/#api-v0-repo-gc that need to be improved to indicate streaming response is the default. So... either you buffer entire response in memory and put it in array |
as discussed with @lidel the response code is enough for us and we should not alert about json parsing errors, added PR about it |
Verified
Steps to verify:
Verified:
Verification passed on
Verified:
Verified passed with
Verified:
|
Description
Found while testing #13554.
Performing a garbage-collection sweep via the button on
brave://ipfs
throws"Garbage collection error: Line: 2, column: 1, Unexpected data after root element."
Steps to Reproduce
brave://ipfs
Install and start
Perform a garbage collection sweep
Actual result:
Throws "Garbage collection error: Line: 2, column: 1, Unexpected data after root element" error
Expected result:
Reproduces how often:
Brave version (brave://version info)
Version/Channel Information:
cc: @bbondy @spylogsster
The text was updated successfully, but these errors were encountered: