Closed ssfrr closed 9 years ago
I get this as well. I updated my julia 0.4 build today, didn't see this error before that. I don't know which build of 0.4 I had installed previously. I'm on Windows.
Yeah, me too. Also on Windows. And this definitely is a regression, but I'm not sure that it really was because of updating julia -- I got the error after updating Julia, Atom.jl and atom-julia-client... Did you update any packages/Juno or only Julia, @davidanthoff?
I can't tell anymore, I probably updated other things as well...
I think for me it was just Julia; I still have a 10-day old 0.4-dev master installed on my main machine (won't touch it as it's currently running perfectly and I have a PhD thesis to submit in <4 weeks!) and there are no errors, although Atom.jl, julia-client and ink are up-to-date (I believe).
My main machine is Win7, my Surface (that produces both this error and the closed #6) runs on Win10.
I'm not seeing this anymore (and didn't update Julia). Did you fix this, @one-more-minute?
I agree, this seems to be fixed on my Surface (with Julia, Atom, Atom.jl and dependencies all up to date) as well. Close this issue?
Yup, this was fixed with @ssfrr's JunoLab/Atom.jl#3. Julia master should fix the upstream issue as well, as it happens, although I haven't tested that yet.
To Reproduce:
1+1
in the console and press enterWhen I run that sequence with a breakpoint on tcp.coffee:12 I see the first time it's called everything is fine (at least it doesn't thrown an exception), but the 2nd time
str
ends up with the valueSo then
lines
ends up being a 5-element array with some empty strings and the first element had two JSON lists that aren't newline separated. At this pointbuffer
still has the first element of"[2,{"inactive":false,"sub":"AudioIO","subInactive":true,"main":"Main"}]"
(the last item that got put in there?) So when it hits the codebuffer[0] += lines.shift()
, the first element of the buffer actually ends up having 3 JSON lists smushed up against each other. Then when it tries to callf
on that string (which tries to parse it) then it throws the exception, probably on the opening bracket of the 2nd smushed message.So as far as I can tell there are 2 bugs here:
I think after the first exception gets called here,
buffer
is hosed and has empty strings in it, which is what then causes #18.Atom Version: 1.0.11 System: Mac OS X 10.10.4 Thrown From: julia-client package, v0.1.2
Stack Trace
Uncaught SyntaxError: Unexpected token [
Commands
Config
Installed Packages