Uncaught SyntaxError: Unexpected end of JSON input about pros-atom3 HOT 18 CLOSED

please remove JSON.parse from your code. Enjoy

from pros-atom3.

At this point I'm pretty sure that this error is non-fatal and can be safely ignored. We'll have to add the code to suppress the notification soon.

from pros-atom3.

I'm not sure why we're getting this error. If you're willing to debug, it would be much appreciated if you could pop a breakpoint on the culprit line (inside @purduesigbots/pros-cli-middleware/dist/util.js:110) to see what the data looks like. If not, we'll add a try/catch to at least print out the line to the console (but that won't really solve the issue)

from pros-atom3.

I am getting this same error.
.

Any help solving this would be appreciated.

from pros-atom3.

I am getting the same error with a new installation of PROS on my system. I am not sure how to proceed

from pros-atom3.

I'm not sure why we're getting this error. If you're willing to debug, it would be much appreciated if you could pop a breakpoint on the culprit line (inside @purduesigbots/pros-cli-middleware/dist/util.js:110) to see what the data looks like. If you'd like help walking through this, join our Slack and we'll be glad to take you through the steps.

from pros-atom3.

I'm getting the same issue, I don't know why. It would be extremely helpful if you could update me on the issue, as in, has there been any solve to it? I'm on macOS btw.

from pros-atom3.

I'm not sure why we're getting this error. If you're willing to debug, it would be much appreciated if you could pop a breakpoint on the culprit line (inside @purduesigbots/pros-cli-middleware/dist/util.js:110) to see what the data looks like. If not, we'll add a try/catch to at least print out the line to the console (but that won't really solve the issue)

I'm not sure why we're getting this error. If you're willing to debug, it would be much appreciated if you could pop a breakpoint on the culprit line (inside @purduesigbots/pros-cli-middleware/dist/util.js:110) to see what the data looks like. If you'd like help walking through this, join our Slack and we'll be glad to take you through the steps.

from pros-atom3.

I don't have a slack account and it doesn't show a sign up page. Are you sure there isn't an easier way to resolve this issue?

from pros-atom3.

We haven't been able to reproduce this issue on our machines, so we don't know what's causing it. That is to say, it would be very enlightening if someone who is running into the issue could help us out debugging it.

You can join the slack workspace using this link instead

from pros-atom3.

What channel would I use to help to debug this error?

from pros-atom3.

I got the same error but after that it said unable to start c++ server I don't know if that has somenthing to do with that or if that's just me

from pros-atom3.

JSON Error.mov.zip
Here's a video of the error.

from pros-atom3.

Apologies for the delay in taking a look at this -- been in a cross country move and settling in to work.

Following up on the discussion in slack. I've opened purduesigbots/pros-cli-middleware#9 to help us debug these issue in the future. In the meantime so we can resolve your issue, will you modify that pros-cli-middleware/dist/util.js file that you put the breakpoint on to the following and let us know the results. With this information we should be able to see what string is causing the error.

if (e.startsWith(PREFIX)) {
    try {
        var jdata = JSON.parse(e.substr(PREFIX.length));
        var primary = jdata.type.split('/')[0];
        _this.emit(primary, jdata);
    }
    catch (error) {
        console.error("Crashing while parsing \"" + e + "\"");
        throw error;
    }
}
else if (e.trim()) {
    console.log(e);
}

from pros-atom3.

Where would the results be found? Is the code you posted an addition to the modification I made or is it what it should look like right now?

from pros-atom3.

sorry im not in the slack but am experiencing similar issues. Was this ever resolved? Thank you!

from pros-atom3.

please remove JSON.parse from your code. Enjoy

hm. i'm not sure what this would accomplish exactly given that we need to parse the JSON data from the CLI in order to do anything with it, but thanks for the input

from pros-atom3.

i had the same error when i was conveying data from the server to my webpage, the reason for that is i was parsing JSON before the readyState was 4 .

<script type="text/javascript">
const Http = new XMLHttpRequest();
const url='xxxx';

Http.onreadystatechange = function(){

	 if (this.readyState == 4 && this.status == 200) {
	const b = JSON.parse(Http.responseText);
}		
}

Http.open("POST", url);
Http.send();

</script>

from pros-atom3.