-
Notifications
You must be signed in to change notification settings - Fork 5.9k
SyntaxError: Unexpected end of JSON input #453
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
That error likely isn't causing the |
@kylecarbs The syntax error should be ignored? |
I get same error code-server v1.604-vsc1.32.0 |
the same issue, using AWS EC2 ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20190212 (ami-05af84768964d3dc0) |
I am getting a similar error in my docker logs:
I am trying to run this using docker-compose. The editor loads for me on the port specified, but the project files are not visible.
|
Same problem here in ArchLinux as self hosting. I can access the IDE pointing at localhost:8443 but it doesn't start up on the right directory and I don't seem to be able open any other directory but the current one (which happens to be the one where the |
Also getting the same error with Ubuntu 18.04 |
Im also getting this same WARN Uncaught Exception: Error: Unexpected end of JSON input using Ubuntu 16.04 using the newest binary release |
For me, I don't know how exactly, adding certs and key and forcing an initial directory with The editor seems to work properly now. I am left with another little error |
Just pushed a commit that should permanently resolve the JSON message, but it's very unlikely to have caused any issues (it's just about trying to read the backup workspaces JSON file in order to delete empty workspace storage). I also made the port scanning message more explicit. It now says "Port scanning will not be available because netstat is not installed" and it's been downgraded to a warning. We'll probably need to add some documentation on why we have port scanning and what you lose if you don't have it (assuming we don't replace it: #382). |
When it will be available in any release file? |
can you post an example of the command you're using to get it working? ive been unable to get it running so far. |
Sure, as simple as this: |
This has to deal with how the JSONs were generated in |
I got it working by changing the volume to:
|
When are expecting a fix for this? I've got the same problem with GCP, Digital Ocean and Vultr running Ubuntu 16/18 and it sure seems it is coming from code-server |
Same for me on running Docker release. When I use binaries I don't have this problem ( but it crashes after some minutes with different error ) |
When I use binaries on Ubuntu 16.04, it has the same problem. Using the latest release. |
Same issue: Using Ubuntu 18.04 on Digital Ocean and running
|
same |
same here, but my ubuntu is 16.04 |
I guess I'm the only crazy one trying to get this working in my Fedora29 workspace container, but it seems I'm getting the same errors everyone above is getting that shouldn't be related Fedora as everyone here seems to be running Ubuntu. I'm just downloading the latest binaries and tossing it into my container which technically should work otherwise. |
same error in my Ubuntu18.04.
|
Just made a release that contains the fix. |
code-server
version: 1.691-vsc1.33.0Description
When I tried to run the code-server command, it gives me this error:
WARN Uncaught Exception: Error: Unexpected end of JSON input
SyntaxError: Unexpected end of JSON input
at JSON.parse ()
at pfs_1.readFile.then.contents (/home/travis/build/codercom/code-server/packages/server/build/bootstrap-fork.js.gz:76703:45)
at
at Timeout.setTimeout [as _onTimeout] (/home/travis/build/codercom/code-server/packages/server/build/bootstrap-fork.js.gz:53086:31)
at ontimeout (timers.js:498:11)
at tryOnTimeout (timers.js:323:5)
at Timer.listOnTimeout (timers.js:290:5)
Also, when I tried to connect the website ignoring the error, I received the error
x.x.x.x refused to connect
. (Okay. This is a different issue. I need to specify the specific IP address for the code-server to run on instead of 0.0.0.0)Steps to Reproduce
sudo code-server -p 80
The text was updated successfully, but these errors were encountered: