-
Notifications
You must be signed in to change notification settings - Fork 132
Installation: Failed to parse ... library_index.json #1171
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
Comments
I guess there was a glitch during install that made the download fail. |
Are there any actions that can be taken so that this error doesn't happen? It is pretty reproducible, up to wiping out the whole Eclipse installation and starting afresh. |
It doesn't happen here. |
try to install the product from https://eclipse.baeyens.it/ I'm not sure how the market place handles product installs |
Indeed, manually downloading the file into that location when Eclipse is down and then starting it up makes the "Finishing the installation" get to the next step. Wonder why can't the installer do it on its own, doing it with |
From your error log you can see the file is truncated |
The file doesn't exist (not even the zero length). The platform is Linux, there are no virus checkers. I've got the issue resolved (manual download), so I'll close it now - but if you feel like getting to the root cause and making your product better - I'm willing to help. |
As I said. The file is deleted when it fails to parse. Sloeber does so to avoid the same problem to happen again. It also removes the file from the index files to .. avoid the same thing to happen again. The parsing is done by a json parser that -in your case- says there is an unexpected end of file. Given the other info: the file is not empty. So it must be a download issue, a local issue, or the file changed recently and it manifests on linux (Last tests on linux are from some days ago) and not on windows (just tested it) If it is consistent on your system it would be great if you could debug. The easiest is to compile the SDK and start a debugging session. |
Describe the bug
"Problem occured" dialog box pops up, with the following message:
Note: the file at the specified path doesn't exist.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Product installs.
Screenshots
N/A
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: