[julia-users] Re: Juno stopped working - error message

[Andre P.]

Hi all. I upgraded to 0.4.0 and basically lighttables + Jewel stopped 
working.  The errors are pretty mucb as above.


   - 
   
   WARNING: LightTable.jl: cannot resize array with shared data
in push! at 
/Applications/Julia-0.4.0.app/Contents/Resources/julia/lib/julia/sys.dylib
in read_operator at /Users/Andre/.julia/v0.4/JuliaParser/src/lexer.jl:368
in next_token at /Users/Andre/.julia/v0.4/JuliaParser/src/lexer.jl:752
in qualifiedname at /Users/Andre/.julia/v0.4/Jewel/src/parse/scope.jl:59
in nexttoken at /Users/Andre/.julia/v0.4/Jewel/src/parse/scope.jl:78
in nextscope! at /Users/Andre/.julia/v0.4/Jewel/src/parse/scope.jl:116
in scopes at /Users/Andre/.julia/v0.4/Jewel/src/parse/scope.jl:149
[inlined code] from /Users/Andre/.julia/v0.4/Lazy/src/macros.jl:141
in codemodule at /Users/Andre/.julia/v0.4/Jewel/src/parse/parse.jl:8
in getmodule at /Users/Andre/.julia/v0.4/Jewel/src/eval.jl:42
in anonymous at /Users/Andre/.julia/v0.4/Jewel/src/LightTable/eval.jl:51
in handlecmd at 
/Users/Andre/.julia/v0.4/Jewel/src/LightTable/LightTable.jl:70
in handlenext at 
/Users/Andre/.julia/v0.4/Jewel/src/LightTable/LightTable.jl:86
in server at /Users/Andre/.julia/v0.4/Jewel/src/LightTable/LightTable.jl:27
in server at /Users/Andre/.julia/v0.4/Jewel/src/Jewel.jl:23
in include at 
/Applications/Julia-0.4.0.app/Contents/Resources/julia/lib/julia/sys.dylib
in include_from_node1 at 
/Applications/Julia-0.4.0.app/Contents/Resources/julia/lib/julia/sys.dylib
in process_options at 
/Applications/Julia-0.4.0.app/Contents/Resources/julia/lib/julia/sys.dylib
in _start at 
/Applications/Julia-0.4.0.app/Contents/Resources/julia/lib/julia/sys.dylib
   
   - 
   
   
   
 I can no longer use Lighttable because of this. Tried some of the fixes 
above but no seemed to work. Has this been solved some how?

Julia Version 0.4.0

Commit 0ff703b* (2015-10-08 06:20 UTC)

Platform Info:

  System: Darwin (x86_64-apple-darwin13.4.0)

  CPU: Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz

  WORD_SIZE: 64

  BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Haswell)

  LAPACK: libopenblas64_

  LIBM: libopenlibm

  LLVM: libLLVM-3.3


THANKS,


Andre

[julia-users] Re: Juno stopped working - error message

[Sisyphuss]

Juno works fine for me on 0.4.0-rc1+33


On Friday, September 18, 2015 at 6:35:56 PM UTC+2, Serge Santos wrote:
>
> Hi,
>
> Juno was working fine, but I had to restart Juno and now it keeps churning 
> after successfully connecting with Julia but I cannot use the shell to work 
> (nothing happen). There are no reasons why it should not work anymore.
>
> All the Julia packages are updated and up-to-date and I even reinstalled 
> Julia and Juno. It has not changed anything. 
>
> Any help / advise is highly appreciated (it is quite frustrating).
>
> Here is the error message:
>
>
>- 
>
>WARNING: LightTable.jl: type cannot be constructed
> in utf8sizeof at C:\Users\Serge\.julia\v0.3\JuliaParser\src\lexer.jl:322
> in skip_to_eol at C:\Users\Serge\.julia\v0.3\JuliaParser\src\lexer.jl:349
> in lexcomment at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:27
> in nexttoken at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:74
> in nextscope! at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:116
> in scopes at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:149
> in codemodule at C:\Users\Serge\.julia\v0.3\Jewel\src\parse/parse.jl:141
> in filemodule at C:\Users\Serge\.julia\v0.3\Jewel\src\module.jl:93
> in anonymous at C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable\misc.jl:5
> in handlecmd at 
> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:65
> in handlenext at 
> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:81
> in server at 
> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:22
> in server at C:\Users\Serge\.julia\v0.3\Jewel\src\Jewel.jl:18
> in include at boot.jl:245
> in include_from_node1 at loading.jl:128
> in process_options at client.jl:285
> in _start at client.jl:354
>
>- 
>
>symbol could not be found jl_generating_output (-1): The specified 
> procedure could not be found.
>
>
>- 
>
>Invalid behavior: :lt.objs.clients.tcp/send!
>
>- 
>
>Error: This socket has been ended by the other party
>at Socket.writeAfterFIN [as write] (net.js:275:12)
>at lt.objs.clients.tcp.send_to 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:32857:96)
>at Function.lt.objs.clients.tcp.__BEH__send_BANG_ 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:32937:38)
>at c 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:6196:14)
>at a 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:6236:18)
>at c 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:20443:76)
>at a 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:20477:18)
>at a 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:20488:34)
>at b 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:20492:14)
>at Function.lt.objs.clients.__BEH__try_send 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:28855:189)
>
>
>

[julia-users] Re: Juno stopped working - error message

[Haoran Jiang]

Hi Greg, I am new to Julia and Juno, I just installed this software today 
and I have the same error message as you do, can you tell me what did you 
do to make it right? this is my Pkg.status. I never had it worked 
before(since it is my first day install it) so i dont know what file to 
change and where to change them, Thanks!


在 2015年9月20日星期日 UTC-7下午6:09:56，Greg Plowman写道：
>
> Serge,
>
> Below is output of Pkg.status():
>
> I had previously tried removing many packages, but nothing is pinned (so 
> not sure if rolling back will result in same config)
>
> The only error message I receive using Juno is:
> symbol could not be found jl_generating_output (-1): The specified 
> procedure could not be found.
>
> but after this everything seems to work as normal.
>
> Hope this helps.
> -- Greg
>
>
>_
>_   _ _(_)_ |  A fresh approach to technical computing
>   (_) | (_) (_)|  Documentation: http://docs.julialang.org
>_ _   _| |_  __ _   |  Type "help()" for help.
>   | | | | | | |/ _` |  |
>   | | |_| | | | (_| |  |  Version 0.3.11 (2015-07-27 06:18 UTC)
>  _/ |\__'_|_|_|\__'_|  |  Official http://julialang.org/ release
> |__/   |  x86_64-w64-mingw32
> julia> Pkg.status()
> 9 required packages:
>  - Dates 0.3.2
>  - Distributions 0.8.6
>  - HDF5  0.5.5
>  - ImageView 0.1.16
>  - Images0.4.47
>  - JLD   0.5.4
>  - Jewel 1.0.6
>  - Optim 0.4.2
>  - ZMQ   0.2.0
> 39 additional packages:
>  - ArrayViews0.6.3
>  - BinDeps   0.3.15
>  - Blosc 0.1.4
>  - Cairo 0.2.30
>  - Calculus  0.1.10
>  - ColorTypes0.1.4
>  - ColorVectorSpace  0.0.3
>  - Colors0.5.3
>  - Compat0.7.1
>  - Compose   0.3.15
>  - DataStructures0.3.12
>  - Docile0.5.18
>  - DualNumbers   0.1.3
>  - FactCheck 0.4.0
>  - FixedPointNumbers 0.0.10
>  - Graphics  0.1.0
>  - HttpCommon0.1.2
>  - IniFile   0.2.4
>  - Iterators 0.1.8
>  - JSON  0.4.5
>  - JuliaParser   0.6.2
>  - LNR   0.0.1
>  - Lazy  0.10.0
>  - LibExpat  0.0.8
>  - MacroTools0.2.0
>  - NaNMath   0.1.0
>  - PDMats0.3.5
>  - Reexport  0.0.3
>  - Requires  0.2.0
>  - SHA   0.1.1
>  - SIUnits   0.0.5
>  - StatsBase 0.7.2
>  - StatsFuns 0.1.3
>  - TexExtensions 0.0.2
>  - Tk0.3.6
>  - URIParser 0.0.7
>  - WinRPM0.1.12
>  - Winston   0.11.12
>  - Zlib  0.1.9
> Julia>
>
>
>
> On Monday, September 21, 2015 at 9:44:24 AM UTC+10, Serge Santos wrote:
>
> Hi All,
>
> I tried to roll back to JuliaParser v0.6.2 and it didn't work. 
>
> If someone still manages to successfully run Juno with Julia 0.3.11, can 
> you please send the list of packages with version numbers that does not 
> create any issues with Juno (i.e,, output from Pkg.status()). I was not 
> able to figure out what combination of versions work. 
>
> Many thanks in advance
> Serge
>
> On Monday, 21 September 2015 00:16:27 UTC+1, Greg Plowman wrote:
>
> Hi All,
>
> On 2 different PCs where Juno works (almost without error) Pkg.status() 
> reports JuliaParser v0.6.2
> On PC that has Juno errors, Pkg.status() reports JuliaParser v0.6.3
> Rolling back to JuliaParser v0.1.2 creates different errors.
> So it seems we need to revert to JuliaParser v0.6.2
>
> I'm not at a PC where I can see if we can pin v0.6.2, in light of the 
> following:
>
> Before this JuliaParser was at version v0.6.3, are you sure we should try 
> reverting to v0.1.2?
>
> See the tagged versions 
>
> https://github.com/jakebolewski/JuliaParser.jl/releases. So that’s the 
> next latest tagged version. You could probably checkout a specific commit 
> prior to the commit that’s causing the breakage instead though.
>
> Also, I don't want to play around with Pkg.ANYTHING on a working 
> configuration at the moment :)
>
> -- Greg
>
>
> On Monday, September 21, 2015 at 4:50:37 AM UTC+10, Tony Kelman wrote:
>
> What's temporarily broken here is some of the packages that 
> Light-Table-based Juno relies on to work. In the meantime you can still use 
> command-line REPL Julia, and while it's not the most friendly interface 
> your 

Re: [julia-users] Re: Juno stopped working - error message

[Spencer Russell]

Hi Haoran,

Try pinning the Compat package by running `Pkg.pin("Compat", v"0.7.0")`

If you're running Julia 0.3.11 that should be the newest version that
will install, so I'm not sure how you ended up with Compat 0.7.3 (which
is currently tagged to be 0.4 and newer). That's a pretty recent change
though(yesterday evening), but if you just installed today I'd think
you'd be good to go.

-s


On Tue, Sep 22, 2015, at 02:58 AM, Haoran Jiang wrote:
> Hi Greg, I am new to Julia and Juno, I just installed this software
> today and I have the same error message as you do, can you tell me
> what did you do to make it right? this is my Pkg.status. I never had
> it worked before(since it is my first day install it) so i dont know
> what file to change and where to change them, Thanks!
>
>
> 在 2015年9月20日星期日 UTC-7下午6:09:56，Greg Plowman写道：
>> Serge,
>>
>> Below is output of Pkg.status():
>>
>> I had previously tried removing many packages, but nothing is pinned
>> (so not sure if rolling back will result in same config)
>>
>> The only error message I receive using Juno is:    symbol could not
>> be found jl_generating_output (-1): The specified procedure could not
>> be found.
>>
>> but after this everything seems to work as normal.
>>
>> Hope this helps. -- Greg
>>
>>
>>
>> _   _   _ _(_)_ |  A fresh approach to technical computing
>> (_) | (_) (_)    |  Documentation: http://docs.julialang.org   _
>> _   _| |_  __ _   |  Type "help()" for help.  | | | | | | |/ _` |  |
>> | | |_| | | | (_| |  |  Version 0.3.11 (2015-07-27 06:18 UTC) _/
>> |\__'_|_|_|\__'_|  |  Official http://julialang.org/ release
>> |__/   |  x86_64-w64-mingw32
>> julia> Pkg.status()
>> 9 required packages: - Dates 0.3.2 -
>> Distributions 0.8.6 - HDF5
>> 0.5.5 - ImageView 0.1.16 - Images
>> 0.4.47 - JLD   0.5.4 - Jewel
>> 1.0.6 - Optim 0.4.2 - ZMQ
>> 0.2.0 39 additional packages: - ArrayViews
>> 0.6.3 - BinDeps   0.3.15 - Blosc
>> 0.1.4 - Cairo 0.2.30 - Calculus
>> 0.1.10 - ColorTypes    0.1.4 -
>> ColorVectorSpace  0.0.3 - Colors
>> 0.5.3 - Compat    0.7.1 - Compose
>> 0.3.15 - DataStructures    0.3.12 - Docile
>> 0.5.18 - DualNumbers   0.1.3 - FactCheck
>> 0.4.0 - FixedPointNumbers 0.0.10 - Graphics
>> 0.1.0 - HttpCommon    0.1.2 - IniFile
>> 0.2.4 - Iterators 0.1.8 - JSON
>> 0.4.5 - JuliaParser   0.6.2 - LNR
>> 0.0.1 - Lazy  0.10.0 - LibExpat
>> 0.0.8 - MacroTools    0.2.0 - NaNMath
>> 0.1.0 - PDMats    0.3.5 - Reexport
>> 0.0.3 - Requires  0.2.0 - SHA
>> 0.1.1 - SIUnits   0.0.5 - StatsBase
>> 0.7.2 - StatsFuns 0.1.3 - TexExtensions
>> 0.0.2 - Tk    0.3.6 - URIParser
>> 0.0.7 - WinRPM    0.1.12 - Winston
>> 0.11.12 - Zlib  0.1.9
>> Julia>
>>
>>
>>
>>
>> On Monday, September 21, 2015 at 9:44:24 AM UTC+10, Serge
>> Santos wrote:
>>> Hi All,
>>>
>>> I tried to roll back to JuliaParser v0.6.2 and it didn't work.
>>>
>>> If someone still manages to successfully run Juno with Julia 0.3.11,
>>> can you please send the list of packages with version numbers that
>>> does not create any issues with Juno (i.e,, output from
>>> Pkg.status()). I was not able to figure out what combination of
>>> versions work.
>>>
>>> Many thanks in advance Serge
>>>
>>> On Monday, 21 September 2015 00:16:27 UTC+1, Greg Plowman  wrote:
 Hi All,

 On 2 different PCs where Juno works (almost without error)
 Pkg.status() reports JuliaParser v0.6.2 On PC that has Juno errors,
 Pkg.status() reports JuliaParser v0.6.3 Rolling back to JuliaParser
 v0.1.2 creates different errors. So it seems we need to revert to
 JuliaParser v0.6.2

 I'm not at a PC where I can see if we can pin v0.6.2, in light of
 the following:



>> Before this JuliaParser was at version v0.6.3, are you sure we
>> should try reverting to v0.1.2?






> See the tagged versions
> https://github.com/jakebolewski/JuliaParser.jl/releases. So that’s
> the next latest tagged version. You could probably checkout a
> specific commit prior to the commit that’s causing the breakage
> instead though.









 Also, I don't want to play around with Pkg.ANYTHING on a working
 configuration at the moment :)



 -- Greg


 On Monday, September 21, 2015 at 4:50:37 AM UTC+10, Tony Kelman
 wrote:
> What's temporarily broken here is some of the packages that Light-Table-
> based Juno relies on to work. In the meantime you can still use
> command-line REPL Julia, and while it's not the most 

Re: [julia-users] Re: Juno stopped working - error message

[Haoran Jiang]

Hi Spencer:
Thanks for the reply! However, I just tried the method you told me but it 
still doesn't work. 
I also tried to pinned back everything just like how Serge was doing, but 
it still doesn't work, here is my status now.


在 2015年9月22日星期二 UTC-7上午11:13:50，Spencer Russell写道：
>
> Hi Haoran,
>  
> Try pinning the Compat package by running `Pkg.pin("Compat", v"0.7.0")`
>  
> If you're running Julia 0.3.11 that should be the newest version that will 
> install, so I'm not sure how you ended up with Compat 0.7.3 (which is 
> currently tagged to be 0.4 and newer). That's a pretty recent change 
> though(yesterday evening), but if you just installed today I'd think you'd 
> be good to go.
>  
> -s
>  
>  
> On Tue, Sep 22, 2015, at 02:58 AM, Haoran Jiang wrote:
>
> Hi Greg, I am new to Julia and Juno, I just installed this software today 
> and I have the same error message as you do, can you tell me what did you 
> do to make it right? this is my Pkg.status. I never had it worked 
> before(since it is my first day install it) so i dont know what file to 
> change and where to change them, Thanks!
>  
>  
> 在 2015年9月20日星期日 UTC-7下午6:09:56，Greg Plowman写道：
>
> Serge,
>  
> Below is output of Pkg.status():
>  
> I had previously tried removing many packages, but nothing is pinned (so 
> not sure if rolling back will result in same config)
>  
> The only error message I receive using Juno is:
> symbol could not be found jl_generating_output (-1): The specified 
> procedure could not be found.
>  
> but after this everything seems to work as normal.
>  
> Hope this helps.
> -- Greg
>  
>  
>
>_
>_   _ _(_)_ |  A fresh approach to technical computing
>   (_) | (_) (_)|  Documentation: http://docs.julialang.org
>_ _   _| |_  __ _   |  Type "help()" for help.
>   | | | | | | |/ _` |  |
>   | | |_| | | | (_| |  |  Version 0.3.11 (2015-07-27 06:18 UTC)
>  _/ |\__'_|_|_|\__'_|  |  Official http://julialang.org/ release
> |__/   |  x86_64-w64-mingw32
> julia> Pkg.status()
> 9 required packages:
>  - Dates 0.3.2
>  - Distributions 0.8.6
>  - HDF5  0.5.5
>  - ImageView 0.1.16
>  - Images0.4.47
>  - JLD   0.5.4
>  - Jewel 1.0.6
>  - Optim 0.4.2
>  - ZMQ   0.2.0
> 39 additional packages:
>  - ArrayViews0.6.3
>  - BinDeps   0.3.15
>  - Blosc 0.1.4
>  - Cairo 0.2.30
>  - Calculus  0.1.10
>  - ColorTypes0.1.4
>  - ColorVectorSpace  0.0.3
>  - Colors0.5.3
>  - Compat0.7.1
>  - Compose   0.3.15
>  - DataStructures0.3.12
>  - Docile0.5.18
>  - DualNumbers   0.1.3
>  - FactCheck 0.4.0
>  - FixedPointNumbers 0.0.10
>  - Graphics  0.1.0
>  - HttpCommon0.1.2
>  - IniFile   0.2.4
>  - Iterators 0.1.8
>  - JSON  0.4.5
>  - JuliaParser   0.6.2
>  - LNR   0.0.1
>  - Lazy  0.10.0
>  - LibExpat  0.0.8
>  - MacroTools0.2.0
>  - NaNMath   0.1.0
>  - PDMats0.3.5
>  - Reexport  0.0.3
>  - Requires  0.2.0
>  - SHA   0.1.1
>  - SIUnits   0.0.5
>  - StatsBase 0.7.2
>  - StatsFuns 0.1.3
>  - TexExtensions 0.0.2
>  - Tk0.3.6
>  - URIParser 0.0.7
>  - WinRPM0.1.12
>  - Winston   0.11.12
>  - Zlib  0.1.9
> Julia>
>
>  
>  
>  
> On Monday, September 21, 2015 at 9:44:24 AM UTC+10, Serge Santos wrote:
>
> Hi All,
>  
> I tried to roll back to JuliaParser v0.6.2 and it didn't work. 
>  
> If someone still manages to successfully run Juno with Julia 0.3.11, can 
> you please send the list of packages with version numbers that does not 
> create any issues with Juno (i.e,, output from Pkg.status()). I was not 
> able to figure out what combination of versions work. 
>  
> Many thanks in advance
> Serge
>  
> On Monday, 21 September 2015 00:16:27 UTC+1, Greg Plowman wrote:
>
> Hi All,
>  
> On 2 different PCs where Juno works (almost without error) Pkg.status() 
> reports JuliaParser v0.6.2
> On PC that has Juno errors, Pkg.status() reports JuliaParser v0.6.3
> Rolling back to JuliaParser v0.1.2 creates different errors.
> So it seems we need to revert to JuliaParser v0.6.2
>  
> I'm not at a PC where I can 

Re: [julia-users] Re: Juno stopped working - error message

[Haoran Jiang]

here is the screen copy of my error message,what do you suggest i to do?



在 2015年9月22日星期二 UTC-7下午8:50:00，Spencer Russell写道：
>
> Can you cut/paste your session with the error into a gist? That might help 
> track down more specifically what’s causing the issue.
>
> -s
>
> On Sep 22, 2015, at 11:46 PM, Haoran Jiang  > wrote:
>
> Hi Spencer:
> Thanks for the reply! However, I just tried the method you told me but it 
> still doesn't work. 
> I also tried to pinned back everything just like how Serge was doing, but 
> it still doesn't work, here is my status now.
>
>
> 在 2015年9月22日星期二 UTC-7上午11:13:50，Spencer Russell写道：
>
> Hi Haoran,
>  
> Try pinning the Compat package by running `Pkg.pin("Compat", v"0.7.0")`
>  
> If you're running Julia 0.3.11 that should be the newest version that will 
> install, so I'm not sure how you ended up with Compat 0.7.3 (which is 
> currently tagged to be 0.4 and newer). That's a pretty recent change 
> though(yesterday evening), but if you just installed today I'd think you'd 
> be good to go.
>  
> -s
>  
>  
> On Tue, Sep 22, 2015, at 02:58 AM, Haoran Jiang wrote:
>
> Hi Greg, I am new to Julia and Juno, I just installed this software today 
> and I have the same error message as you do, can you tell me what did you 
> do to make it right? this is my Pkg.status. I never had it worked 
> before(since it is my first day install it) so i dont know what file to 
> change and where to change them, Thanks!
>  
>  
> 在 2015年9月20日星期日 UTC-7下午6:09:56，Greg Plowman写道：
>
> Serge,
>  
> Below is output of Pkg.status():
>  
> I had previously tried removing many packages, but nothing is pinned (so 
> not sure if rolling back will result in same config)
>  
> The only error message I receive using Juno is:
> symbol could not be found jl_generating_output (-1): The specified 
> procedure could not be found.
>  
> but after this everything seems to work as normal.
>  
> Hope this helps.
> -- Greg
>  
>  
>
>_
>_   _ _(_)_ |  A fresh approach to technical computing
>   (_) | (_) (_)|  Documentation: http://docs.julialang.org
>_ _   _| |_  __ _   |  Type "help()" for help.
>   | | | | | | |/ _` |  |
>   | | |_| | | | (_| |  |  Version 0.3.11 (2015-07-27 06:18 UTC)
>  _/ |\__'_|_|_|\__'_|  |  Official http://julialang.org/ release
> |__/   |  x86_64-w64-mingw32
> julia> Pkg.status()
> 9 required packages:
>  - Dates 0.3.2
>  - Distributions 0.8.6
>  - HDF5  0.5.5
>  - ImageView 0.1.16
>  - Images0.4.47
>  - JLD   0.5.4
>  - Jewel 1.0.6
>  - Optim 0.4.2
>  - ZMQ   0.2.0
> 39 additional packages:
>  - ArrayViews0.6.3
>  - BinDeps   0.3.15
>  - Blosc 0.1.4
>  - Cairo 0.2.30
>  - Calculus  0.1.10
>  - ColorTypes0.1.4
>  - ColorVectorSpace  0.0.3
>  - Colors0.5.3
>  - Compat0.7.1
>  - Compose   0.3.15
>  - DataStructures0.3.12
>  - Docile0.5.18
>  - DualNumbers   0.1.3
>  - FactCheck 0.4.0
>  - FixedPointNumbers 0.0.10
>  - Graphics  0.1.0
>  - HttpCommon0.1.2
>  - IniFile   0.2.4
>  - Iterators 0.1.8
>  - JSON  0.4.5
>  - JuliaParser   0.6.2
>  - LNR   0.0.1
>  - Lazy  0.10.0
>  - LibExpat  0.0.8
>  - MacroTools0.2.0
>  - NaNMath   0.1.0
>  - PDMats0.3.5
>  - Reexport  0.0.3
>  - Requires  0.2.0
>  - SHA   0.1.1
>  - SIUnits   0.0.5
>  - StatsBase 0.7.2
>  - StatsFuns 0.1.3
>  - TexExtensions 0.0.2
>  - Tk0.3.6
>  - URIParser 0.0.7
>  - WinRPM0.1.12
>  - Winston   0.11.12
>  - Zlib  0.1.9
> Julia>
>
>  
>  
>  
> On Monday, September 21, 2015 at 9:44:24 AM UTC+10, Serge Santos wrote:
>
> Hi All,
>  
> I tried to roll back to JuliaParser v0.6.2 and it didn't work. 
>  
> If someone still manages to successfully run Juno with Julia 0.3.11, can 
> you please send the list of packages with version numbers that does not 
> create any issues with Juno (i.e,, output from Pkg.status()). I was not 
> able to figure out what combination of versions work. 
>  
> Many thanks in advance
> Serge
>  
> On Monday, 21 September 2015 00:16:27 

Re: [julia-users] Re: Juno stopped working - error message

[Spencer Russell]

Can you cut/paste your session with the error into a gist? That might help 
track down more specifically what’s causing the issue.

-s

> On Sep 22, 2015, at 11:46 PM, Haoran Jiang  wrote:
> 
> Hi Spencer:
> Thanks for the reply! However, I just tried the method you told me but it 
> still doesn't work. 
> I also tried to pinned back everything just like how Serge was doing, but it 
> still doesn't work, here is my status now.
> 
> 
> 在 2015年9月22日星期二 UTC-7上午11:13:50，Spencer Russell写道：
> Hi Haoran,
>  
> Try pinning the Compat package by running `Pkg.pin("Compat", v"0.7.0")`
>  
> If you're running Julia 0.3.11 that should be the newest version that will 
> install, so I'm not sure how you ended up with Compat 0.7.3 (which is 
> currently tagged to be 0.4 and newer). That's a pretty recent change 
> though(yesterday evening), but if you just installed today I'd think you'd be 
> good to go.
>  
> -s
>  
>  
> On Tue, Sep 22, 2015, at 02:58 AM, Haoran Jiang wrote:
> Hi Greg, I am new to Julia and Juno, I just installed this software today and 
> I have the same error message as you do, can you tell me what did you do to 
> make it right? this is my Pkg.status. I never had it worked before(since it 
> is my first day install it) so i dont know what file to change and where to 
> change them, Thanks!
>  
>  
> 在 2015年9月20日星期日 UTC-7下午6:09:56，Greg Plowman写道：
> Serge,
>  
> Below is output of Pkg.status():
>  
> I had previously tried removing many packages, but nothing is pinned (so not 
> sure if rolling back will result in same config)
>  
> The only error message I receive using Juno is:
> symbol could not be found jl_generating_output (-1): The specified 
> procedure could not be found.
>  
> but after this everything seems to work as normal.
>  
> Hope this helps.
> -- Greg
>  
>  
> 
>_
>_   _ _(_)_ |  A fresh approach to technical computing
>   (_) | (_) (_)|  Documentation: http://docs.julialang.org 
> 
>_ _   _| |_  __ _   |  Type "help()" for help.
>   | | | | | | |/ _` |  |
>   | | |_| | | | (_| |  |  Version 0.3.11 (2015-07-27 06:18 UTC)
>  _/ |\__'_|_|_|\__'_|  |  Official http://julialang.org/ 
>  release
> |__/   |  x86_64-w64-mingw32
> julia> Pkg.status()
> 9 required packages:
>  - Dates 0.3.2
>  - Distributions 0.8.6
>  - HDF5  0.5.5
>  - ImageView 0.1.16
>  - Images0.4.47
>  - JLD   0.5.4
>  - Jewel 1.0.6
>  - Optim 0.4.2
>  - ZMQ   0.2.0
> 39 additional packages:
>  - ArrayViews0.6.3
>  - BinDeps   0.3.15
>  - Blosc 0.1.4
>  - Cairo 0.2.30
>  - Calculus  0.1.10
>  - ColorTypes0.1.4
>  - ColorVectorSpace  0.0.3
>  - Colors0.5.3
>  - Compat0.7.1
>  - Compose   0.3.15
>  - DataStructures0.3.12
>  - Docile0.5.18
>  - DualNumbers   0.1.3
>  - FactCheck 0.4.0
>  - FixedPointNumbers 0.0.10
>  - Graphics  0.1.0
>  - HttpCommon0.1.2
>  - IniFile   0.2.4
>  - Iterators 0.1.8
>  - JSON  0.4.5
>  - JuliaParser   0.6.2
>  - LNR   0.0.1
>  - Lazy  0.10.0
>  - LibExpat  0.0.8
>  - MacroTools0.2.0
>  - NaNMath   0.1.0
>  - PDMats0.3.5
>  - Reexport  0.0.3
>  - Requires  0.2.0
>  - SHA   0.1.1
>  - SIUnits   0.0.5
>  - StatsBase 0.7.2
>  - StatsFuns 0.1.3
>  - TexExtensions 0.0.2
>  - Tk0.3.6
>  - URIParser 0.0.7
>  - WinRPM0.1.12
>  - Winston   0.11.12
>  - Zlib  0.1.9
> Julia>
> 
>  
>  
>  
> On Monday, September 21, 2015 at 9:44:24 AM UTC+10, Serge Santos wrote:
> Hi All,
>  
> I tried to roll back to JuliaParser v0.6.2 and it didn't work. 
>  
> If someone still manages to successfully run Juno with Julia 0.3.11, can you 
> please send the list of packages with version numbers that does not create 
> any issues with Juno (i.e,, output from Pkg.status()). I was not able to 
> figure out what combination of versions work. 
>  
> Many thanks in advance
> Serge
>  
> On Monday, 21 September 2015 00:16:27 UTC+1, Greg Plowman wrote:
> Hi All,
>  
> On 2 different PCs where Juno works 

[julia-users] Re: Juno stopped working - error message

['Greg Plowman' via julia-users]

Hi,

I tried Pkg.pin("JuliaParser", v"0.1.2") but now I get the following error 
(multiple times).

Before this JuliaParser was at version v0.6.3, are you sure we should try 
reverting to v0.1.2?


WARNING: LightTable.jl: `skipws` has no method matching skipws(::TokenStream
)
 in scopes at C:\Users\Greg\.julia\v0.3\Jewel\src\parse\scope.jl:148
 in codemodule at C:\Users\Greg\.julia\v0.3\Jewel\src\parse/parse.jl:141
 in filemodule at C:\Users\Greg\.julia\v0.3\Jewel\src\module.jl:93
 in anonymous at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable\misc.jl:5
 in handlecmd at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/LightTable.
jl:65
 in handlenext at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/LightTable.
jl:81
 in server at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:
22
 in server at C:\Users\Greg\.julia\v0.3\Jewel\src\Jewel.jl:18
 in include at boot.jl:245
 in include_from_node1 at loading.jl:128
 in process_options at client.jl:285
 in _start at client.jl:354



Any other suggestions?

--Greg


On Sunday, September 20, 2015 at 6:16:10 PM UTC+10, Michael Hatherly wrote:

> The type cannot be constructed error should be fixed on 0.3 by 
> https://github.com/jakebolewski/JuliaParser.jl/pull/25. In the mean time 
> you could Pkg.pin("JuliaParser", v"0.1.2") and see if that fixes the 
> problem on Julia 0.3. (Or a version earlier than v"0.1.2" if needed.)
>
> I’ve come across the cannot resize array with shared data error a while 
> ago with the Atom-based Juno. It was fixed by Pkg.checkouting all the 
> involved packages. Might be the same for the LightTable-base Juno, worth a 
> try maybe.
>
> — Mike
> On Saturday, 19 September 2015 19:09:22 UTC+2, Serge Santos wrote:
>>
>> I tried to solve the problem by running Julia 0.4.0-rc2 instead of Julia 
>> 0.3.11. I manage to execute a few commands in Juno, but juno/julia is stuck 
>> as before. The error message is slightly different though:
>>
>>
>>- 
>>
>>WARNING: LightTable.jl: cannot resize array with shared data
>> in push! at array.jl:430
>> in read_operator at 
>> C:\Users\Serge\.julia\v0.4\JuliaParser\src\lexer.jl:368
>> in next_token at C:\Users\Serge\.julia\v0.4\JuliaParser\src\lexer.jl:752
>> in qualifiedname at 
>> C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:59
>> in nexttoken at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:78
>> in nextscope! at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:116
>> in scopes at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:149
>> [inlined code] from C:\Users\Serge\.julia\v0.4\Lazy\src\macros.jl:141
>> in codemodule at C:\Users\Serge\.julia\v0.4\Jewel\src\parse/parse.jl:8
>> in getmodule at C:\Users\Serge\.julia\v0.4\Jewel\src\eval.jl:42
>> in anonymous at 
>> C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable\eval.jl:51
>> in handlecmd at 
>> C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:65
>> in handlenext at 
>> C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:81
>> in server at 
>> C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:22
>> in server at C:\Users\Serge\.julia\v0.4\Jewel\src\Jewel.jl:18
>> in include at boot.jl:261
>> in include_from_node1 at loading.jl:304
>> in process_options at client.jl:308
>> in _start at client.jl:411
>>
>>
>>
>> On Saturday, 19 September 2015 10:40:49 UTC+1, JKPie wrote:
>>>
>>> I have the same problem, I have spent couple of hours reinstalling Julia 
>>> and Juno on Windows and Linux with no result. The code works fine, when I 
>>> call it from command line directly. 
>>> Please help it is freezing my work :/
>>> J
>>>
>>

[julia-users] Re: Juno stopped working - error message

[Michael Hatherly]

The type cannot be constructed error should be fixed on 0.3 by 
https://github.com/jakebolewski/JuliaParser.jl/pull/25. In the mean time 
you could Pkg.pin("JuliaParser", v"0.1.2") and see if that fixes the 
problem on Julia 0.3. (Or a version earlier than v"0.1.2" if needed.)

I’ve come across the cannot resize array with shared data error a while ago 
with the Atom-based Juno. It was fixed by Pkg.checkouting all the involved 
packages. Might be the same for the LightTable-base Juno, worth a try maybe.

— Mike
On Saturday, 19 September 2015 19:09:22 UTC+2, Serge Santos wrote:
>
> I tried to solve the problem by running Julia 0.4.0-rc2 instead of Julia 
> 0.3.11. I manage to execute a few commands in Juno, but juno/julia is stuck 
> as before. The error message is slightly different though:
>
>
>- 
>
>WARNING: LightTable.jl: cannot resize array with shared data
> in push! at array.jl:430
> in read_operator at 
> C:\Users\Serge\.julia\v0.4\JuliaParser\src\lexer.jl:368
> in next_token at C:\Users\Serge\.julia\v0.4\JuliaParser\src\lexer.jl:752
> in qualifiedname at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:59
> in nexttoken at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:78
> in nextscope! at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:116
> in scopes at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:149
> [inlined code] from C:\Users\Serge\.julia\v0.4\Lazy\src\macros.jl:141
> in codemodule at C:\Users\Serge\.julia\v0.4\Jewel\src\parse/parse.jl:8
> in getmodule at C:\Users\Serge\.julia\v0.4\Jewel\src\eval.jl:42
> in anonymous at C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable\eval.jl:51
> in handlecmd at 
> C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:65
> in handlenext at 
> C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:81
> in server at 
> C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:22
> in server at C:\Users\Serge\.julia\v0.4\Jewel\src\Jewel.jl:18
> in include at boot.jl:261
> in include_from_node1 at loading.jl:304
> in process_options at client.jl:308
> in _start at client.jl:411
>
>
>
> On Saturday, 19 September 2015 10:40:49 UTC+1, JKPie wrote:
>>
>> I have the same problem, I have spent couple of hours reinstalling Julia 
>> and Juno on Windows and Linux with no result. The code works fine, when I 
>> call it from command line directly. 
>> Please help it is freezing my work :/
>> J
>>
>

[julia-users] Re: Juno stopped working - error message

[Michael Hatherly]

Before this JuliaParser was at version v0.6.3, are you sure we should try 
reverting to v0.1.2?

See the tagged versions 
https://github.com/jakebolewski/JuliaParser.jl/releases. So that’s the next 
latest tagged version. You could probably checkout a specific commit prior 
to the commit that’s causing the breakage instead though.

What version of Jewel.jl and LightTable.jl are you using?

— Mike
​

On Sunday, 20 September 2015 10:56:22 UTC+2, Greg Plowman wrote:
>
> Hi,
>
> I tried Pkg.pin("JuliaParser", v"0.1.2") but now I get the following 
> error (multiple times).
>
> Before this JuliaParser was at version v0.6.3, are you sure we should try 
> reverting to v0.1.2?
>
>
> WARNING: LightTable.jl: `skipws` has no method matching skipws(::
> TokenStream)
>  in scopes at C:\Users\Greg\.julia\v0.3\Jewel\src\parse\scope.jl:148
>  in codemodule at C:\Users\Greg\.julia\v0.3\Jewel\src\parse/parse.jl:141
>  in filemodule at C:\Users\Greg\.julia\v0.3\Jewel\src\module.jl:93
>  in anonymous at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable\misc.jl:5
>  in handlecmd at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/LightTable
> .jl:65
>  in handlenext at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/
> LightTable.jl:81
>  in server at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/LightTable.jl
> :22
>  in server at C:\Users\Greg\.julia\v0.3\Jewel\src\Jewel.jl:18
>  in include at boot.jl:245
>  in include_from_node1 at loading.jl:128
>  in process_options at client.jl:285
>  in _start at client.jl:354
>
>
>
> Any other suggestions?
>
> --Greg
>
>
> On Sunday, September 20, 2015 at 6:16:10 PM UTC+10, Michael Hatherly wrote:
>
>> The type cannot be constructed error should be fixed on 0.3 by 
>> https://github.com/jakebolewski/JuliaParser.jl/pull/25. In the mean time 
>> you could Pkg.pin("JuliaParser", v"0.1.2") and see if that fixes the 
>> problem on Julia 0.3. (Or a version earlier than v"0.1.2" if needed.)
>>
>> I’ve come across the cannot resize array with shared data error a while 
>> ago with the Atom-based Juno. It was fixed by Pkg.checkouting all the 
>> involved packages. Might be the same for the LightTable-base Juno, worth a 
>> try maybe.
>>
>> — Mike
>> On Saturday, 19 September 2015 19:09:22 UTC+2, Serge Santos wrote:
>>>
>>> I tried to solve the problem by running Julia 0.4.0-rc2 instead of Julia 
>>> 0.3.11. I manage to execute a few commands in Juno, but juno/julia is stuck 
>>> as before. The error message is slightly different though:
>>>
>>>
>>>- 
>>>
>>>WARNING: LightTable.jl: cannot resize array with shared data
>>> in push! at array.jl:430
>>> in read_operator at 
>>> C:\Users\Serge\.julia\v0.4\JuliaParser\src\lexer.jl:368
>>> in next_token at C:\Users\Serge\.julia\v0.4\JuliaParser\src\lexer.jl:752
>>> in qualifiedname at 
>>> C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:59
>>> in nexttoken at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:78
>>> in nextscope! at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:116
>>> in scopes at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:149
>>> [inlined code] from C:\Users\Serge\.julia\v0.4\Lazy\src\macros.jl:141
>>> in codemodule at C:\Users\Serge\.julia\v0.4\Jewel\src\parse/parse.jl:8
>>> in getmodule at C:\Users\Serge\.julia\v0.4\Jewel\src\eval.jl:42
>>> in anonymous at 
>>> C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable\eval.jl:51
>>> in handlecmd at 
>>> C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:65
>>> in handlenext at 
>>> C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:81
>>> in server at 
>>> C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:22
>>> in server at C:\Users\Serge\.julia\v0.4\Jewel\src\Jewel.jl:18
>>> in include at boot.jl:261
>>> in include_from_node1 at loading.jl:304
>>> in process_options at client.jl:308
>>> in _start at client.jl:411
>>>
>>>
>>>
>>> On Saturday, 19 September 2015 10:40:49 UTC+1, JKPie wrote:

 I have the same problem, I have spent couple of hours reinstalling 
 Julia and Juno on Windows and Linux with no result. The code works fine, 
 when I call it from command line directly. 
 Please help it is freezing my work :/
 J

>>>

[julia-users] Re: Juno stopped working - error message

[Tony Kelman]

What's temporarily broken here is some of the packages that 
Light-Table-based Juno relies on to work. In the meantime you can still use 
command-line REPL Julia, and while it's not the most friendly interface 
your code will still run. Your estimation of the Julia ecosystem's 
robustness is pretty accurate though, if you really want to ensure things 
stay working the best way of doing that right now is keeping all packages 
pinned until you have a chance to thoroughly test the versions that an 
upgrade would give you. We plan on automating some of this testing going 
forward, though in the case of Juno much of the code is being replaced 
right now and the replacements aren't totally ready just yet.


On Sunday, September 20, 2015 at 10:45:01 AM UTC-7, Serge Santos wrote:
>
> Thank you all for your inputs. It tried your suggestions and, 
> unfortunately, it does not work. I tried Atom but, after a good start and 
> some success, it keeps crashing in middle of a calculation (windows 10).
>
> To summarize what I tried with Juno and julia 0.3.11:
> - Compat v.0.7.0 (pinned)
> - JuliaParser V0.1.2  (pinned)
> - Jewel v1.0.6.
>
> I get a first error message, which seems to indicate that Julia cannot 
> generate an output.
>
> *symbol could not be found jl_generating_output (-1): The specified 
> procedure could not be found.*
>
> Followed by:
>
> *WARNING: LightTable.jl: `skipws` has no method matching 
> skipws(::TokenStream)*
> * in scopes at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:148*
> * in codemodule at C:\Users\Serge\.julia\v0.3\Jewel\src\parse/parse.jl:141*
> * in getmodule at C:\Users\Serge\.julia\v0.3\Jewel\src\eval.jl:42*
> * in anonymous at 
> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable\eval.jl:51*
> * in handlecmd at 
> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:65*
> * in handlenext at 
> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:81*
> * in server at 
> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:22*
> * in server at C:\Users\Serge\.julia\v0.3\Jewel\src\Jewel.jl:18*
> * in include at boot.jl:245*
> * in include_from_node1 at loading.jl:128*
> * in process_options at client.jl:285*
> * in _start at client.jl:354*
>
> Looking at dependencies with MetadataTools, I smply got:* nothing.* I 
> assume that Jewel does not have any dependencies.
>
> I have a lot of understanding for the effort that goes into making the 
> Julia project work and a success, but I just lost two days of my life 
> trying to make things work and I have an important deadline ahead that I am 
> likely to miss because I relied on a promising tool that, unfortunately, 
> does not seem robust enough at this stage given the amount of development 
> happening.It makes me wonder if I should not wait until Julia becomes more 
> established and robust and switch to other solutions.
>
> On Sunday, 20 September 2015 16:47:05 UTC+1, Dongning Guo wrote:
>>
>> In case you're stuck, this may be a way out:
>> I installed Atom editor and it seems Julia (v0.5??? nightly build)
>> works with it after installing a few packages.  I'm learning to use
>> the new environment ...
>> See https://github.com/JunoLab/atom-julia-client/tree/master/manual
>>
>>
>> On Sunday, September 20, 2015 at 6:59:02 AM UTC-5, Michael Hatherly wrote:
>>>
>>> I can’t see LightTable listed in Pkg.status() output in either PC
>>>
>>> The LightTable module is part of the Jewel package is seems, 
>>> https://github.com/one-more-minute/Jewel.jl/blob/fb854b0a64047ee642773c0aa824993714ee7f56/src/Jewel.jl#L22,
>>>  
>>> and so won’t show up on Pkg.status() output since it’s not a true 
>>> package by itself. Apologies for the misleading directions there.
>>>
>>> What other packages would Juno depend on?
>>>
>>> You can manually walk through the REQUIRE files to see what Jewel 
>>> depends on, or use MetadataTools to do it:
>>>
>>> julia> using MetadataTools
>>> julia> pkgmeta = get_all_pkg();
>>> julia> graph = make_dep_graph(pkgmeta);
>>> julia> deps = get_pkg_dep_graph("Jewel", graph);
>>> julia> map(println, keys(deps.p_to_i));
>>>
>>> You shouldn’t need to change versions for most, if any, of what’s listed 
>>> though. (Don’t forget to call Pkg.free on each package you pin once 
>>> newer versions of the packages are tagged.) Compat 0.7.1 should be far 
>>> enough back I think.
>>>
>>> — Mike
>>> ​
>>> On Sunday, 20 September 2015 13:29:38 UTC+2, Greg Plowman wrote:

 OK I see that second latest tag is v0.1.2 (17 June 2014). Seems a 
 strange jump.

 But now I understand pinning, I can use a strategy of rolling back 
 Juno-related packages until Juno works again.

 What other packages would Juno depend on?

 To help me in this endeavour, I have access to another PC on which Juno 
 runs (almost) without error.
 Confusingly, Pkg.status() reports JuliaParser v0.6.2 on this second PC
 Jewel is v1.0.6 on both PCs.
 I can't see LightTable listed in 

[julia-users] Re: Juno stopped working - error message

['Greg Plowman' via julia-users]

Hi All,

On 2 different PCs where Juno works (almost without error) Pkg.status() 
reports JuliaParser v0.6.2
On PC that has Juno errors, Pkg.status() reports JuliaParser v0.6.3
Rolling back to JuliaParser v0.1.2 creates different errors.
So it seems we need to revert to JuliaParser v0.6.2

I'm not at a PC where I can see if we can pin v0.6.2, in light of the 
following:

Before this JuliaParser was at version v0.6.3, are you sure we should try 
>> reverting to v0.1.2?
>
> See the tagged versions 

https://github.com/jakebolewski/JuliaParser.jl/releases. So that’s the next 
> latest tagged version. You could probably checkout a specific commit prior 
> to the commit that’s causing the breakage instead though.

Also, I don't want to play around with Pkg.ANYTHING on a working 
configuration at the moment :)

-- Greg


On Monday, September 21, 2015 at 4:50:37 AM UTC+10, Tony Kelman wrote:

> What's temporarily broken here is some of the packages that 
> Light-Table-based Juno relies on to work. In the meantime you can still use 
> command-line REPL Julia, and while it's not the most friendly interface 
> your code will still run. Your estimation of the Julia ecosystem's 
> robustness is pretty accurate though, if you really want to ensure things 
> stay working the best way of doing that right now is keeping all packages 
> pinned until you have a chance to thoroughly test the versions that an 
> upgrade would give you. We plan on automating some of this testing going 
> forward, though in the case of Juno much of the code is being replaced 
> right now and the replacements aren't totally ready just yet.
>
>
> On Sunday, September 20, 2015 at 10:45:01 AM UTC-7, Serge Santos wrote:
>>
>> Thank you all for your inputs. It tried your suggestions and, 
>> unfortunately, it does not work. I tried Atom but, after a good start and 
>> some success, it keeps crashing in middle of a calculation (windows 10).
>>
>> To summarize what I tried with Juno and julia 0.3.11:
>> - Compat v.0.7.0 (pinned)
>> - JuliaParser V0.1.2  (pinned)
>> - Jewel v1.0.6.
>>
>> I get a first error message, which seems to indicate that Julia cannot 
>> generate an output.
>>
>> *symbol could not be found jl_generating_output (-1): The specified 
>> procedure could not be found.*
>>
>> Followed by:
>>
>> *WARNING: LightTable.jl: `skipws` has no method matching 
>> skipws(::TokenStream)*
>> * in scopes at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:148*
>> * in codemodule at 
>> C:\Users\Serge\.julia\v0.3\Jewel\src\parse/parse.jl:141*
>> * in getmodule at C:\Users\Serge\.julia\v0.3\Jewel\src\eval.jl:42*
>> * in anonymous at 
>> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable\eval.jl:51*
>> * in handlecmd at 
>> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:65*
>> * in handlenext at 
>> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:81*
>> * in server at 
>> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:22*
>> * in server at C:\Users\Serge\.julia\v0.3\Jewel\src\Jewel.jl:18*
>> * in include at boot.jl:245*
>> * in include_from_node1 at loading.jl:128*
>> * in process_options at client.jl:285*
>> * in _start at client.jl:354*
>>
>> Looking at dependencies with MetadataTools, I smply got:* nothing.* I 
>> assume that Jewel does not have any dependencies.
>>
>> I have a lot of understanding for the effort that goes into making the 
>> Julia project work and a success, but I just lost two days of my life 
>> trying to make things work and I have an important deadline ahead that I am 
>> likely to miss because I relied on a promising tool that, unfortunately, 
>> does not seem robust enough at this stage given the amount of development 
>> happening.It makes me wonder if I should not wait until Julia becomes more 
>> established and robust and switch to other solutions.
>>
>> On Sunday, 20 September 2015 16:47:05 UTC+1, Dongning Guo wrote:
>>>
>>> In case you're stuck, this may be a way out:
>>> I installed Atom editor and it seems Julia (v0.5??? nightly build)
>>> works with it after installing a few packages.  I'm learning to use
>>> the new environment ...
>>> See https://github.com/JunoLab/atom-julia-client/tree/master/manual
>>>
>>>
>>> On Sunday, September 20, 2015 at 6:59:02 AM UTC-5, Michael Hatherly 
>>> wrote:

 I can’t see LightTable listed in Pkg.status() output in either PC

 The LightTable module is part of the Jewel package is seems, 
 https://github.com/one-more-minute/Jewel.jl/blob/fb854b0a64047ee642773c0aa824993714ee7f56/src/Jewel.jl#L22,
  
 and so won’t show up on Pkg.status() output since it’s not a true 
 package by itself. Apologies for the misleading directions there.

 What other packages would Juno depend on?

 You can manually walk through the REQUIRE files to see what Jewel 
 depends on, or use MetadataTools to do it:

 julia> using MetadataTools
 julia> pkgmeta = get_all_pkg();
 julia> graph = 

[julia-users] Re: Juno stopped working - error message

[Serge Santos]

Hi All,

I tried to roll back to JuliaParser v0.6.2 and it didn't work. 

If someone still manages to successfully run Juno with Julia 0.3.11, can 
you please send the list of packages with version numbers that does not 
create any issues with Juno (i.e,, output from Pkg.status()). I was not 
able to figure out what combination of versions work. 

Many thanks in advance
Serge

On Monday, 21 September 2015 00:16:27 UTC+1, Greg Plowman wrote:
>
> Hi All,
>
> On 2 different PCs where Juno works (almost without error) Pkg.status() 
> reports JuliaParser v0.6.2
> On PC that has Juno errors, Pkg.status() reports JuliaParser v0.6.3
> Rolling back to JuliaParser v0.1.2 creates different errors.
> So it seems we need to revert to JuliaParser v0.6.2
>
> I'm not at a PC where I can see if we can pin v0.6.2, in light of the 
> following:
>
> Before this JuliaParser was at version v0.6.3, are you sure we should try 
>>> reverting to v0.1.2?
>>
>> See the tagged versions 
>
> https://github.com/jakebolewski/JuliaParser.jl/releases. So that’s the 
>> next latest tagged version. You could probably checkout a specific commit 
>> prior to the commit that’s causing the breakage instead though.
>
> Also, I don't want to play around with Pkg.ANYTHING on a working 
> configuration at the moment :)
>
> -- Greg
>
>
> On Monday, September 21, 2015 at 4:50:37 AM UTC+10, Tony Kelman wrote:
>
>> What's temporarily broken here is some of the packages that 
>> Light-Table-based Juno relies on to work. In the meantime you can still use 
>> command-line REPL Julia, and while it's not the most friendly interface 
>> your code will still run. Your estimation of the Julia ecosystem's 
>> robustness is pretty accurate though, if you really want to ensure things 
>> stay working the best way of doing that right now is keeping all packages 
>> pinned until you have a chance to thoroughly test the versions that an 
>> upgrade would give you. We plan on automating some of this testing going 
>> forward, though in the case of Juno much of the code is being replaced 
>> right now and the replacements aren't totally ready just yet.
>>
>>
>> On Sunday, September 20, 2015 at 10:45:01 AM UTC-7, Serge Santos wrote:
>>>
>>> Thank you all for your inputs. It tried your suggestions and, 
>>> unfortunately, it does not work. I tried Atom but, after a good start and 
>>> some success, it keeps crashing in middle of a calculation (windows 10).
>>>
>>> To summarize what I tried with Juno and julia 0.3.11:
>>> - Compat v.0.7.0 (pinned)
>>> - JuliaParser V0.1.2  (pinned)
>>> - Jewel v1.0.6.
>>>
>>> I get a first error message, which seems to indicate that Julia cannot 
>>> generate an output.
>>>
>>> *symbol could not be found jl_generating_output (-1): The specified 
>>> procedure could not be found.*
>>>
>>> Followed by:
>>>
>>> *WARNING: LightTable.jl: `skipws` has no method matching 
>>> skipws(::TokenStream)*
>>> * in scopes at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:148*
>>> * in codemodule at 
>>> C:\Users\Serge\.julia\v0.3\Jewel\src\parse/parse.jl:141*
>>> * in getmodule at C:\Users\Serge\.julia\v0.3\Jewel\src\eval.jl:42*
>>> * in anonymous at 
>>> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable\eval.jl:51*
>>> * in handlecmd at 
>>> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:65*
>>> * in handlenext at 
>>> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:81*
>>> * in server at 
>>> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:22*
>>> * in server at C:\Users\Serge\.julia\v0.3\Jewel\src\Jewel.jl:18*
>>> * in include at boot.jl:245*
>>> * in include_from_node1 at loading.jl:128*
>>> * in process_options at client.jl:285*
>>> * in _start at client.jl:354*
>>>
>>> Looking at dependencies with MetadataTools, I smply got:* nothing.* I 
>>> assume that Jewel does not have any dependencies.
>>>
>>> I have a lot of understanding for the effort that goes into making the 
>>> Julia project work and a success, but I just lost two days of my life 
>>> trying to make things work and I have an important deadline ahead that I am 
>>> likely to miss because I relied on a promising tool that, unfortunately, 
>>> does not seem robust enough at this stage given the amount of development 
>>> happening.It makes me wonder if I should not wait until Julia becomes more 
>>> established and robust and switch to other solutions.
>>>
>>> On Sunday, 20 September 2015 16:47:05 UTC+1, Dongning Guo wrote:

 In case you're stuck, this may be a way out:
 I installed Atom editor and it seems Julia (v0.5??? nightly build)
 works with it after installing a few packages.  I'm learning to use
 the new environment ...
 See https://github.com/JunoLab/atom-julia-client/tree/master/manual


 On Sunday, September 20, 2015 at 6:59:02 AM UTC-5, Michael Hatherly 
 wrote:
>
> I can’t see LightTable listed in Pkg.status() output in either PC
>
> The LightTable module is part of the 

[julia-users] Re: Juno stopped working - error message

['Greg Plowman' via julia-users]

OK I see that second latest tag is v0.1.2 (17 June 2014). Seems a strange 
jump.

But now I understand pinning, I can use a strategy of rolling back 
Juno-related packages until Juno works again.

What other packages would Juno depend on?

To help me in this endeavour, I have access to another PC on which Juno 
runs (almost) without error.
Confusingly, Pkg.status() reports JuliaParser v0.6.2 on this second PC
Jewel is v1.0.6 on both PCs.
I can't see LightTable listed in Pkg.status() output in either PC

I think Compat v0.7.2 is also causing ERROR: @doc not defined issue (
https://groups.google.com/forum/#!topic/julia-users/rsM4hxdkAxg)
so maybe reverting back to Compat v0.7.0 might also help.

-- Greg


On Sunday, September 20, 2015 at 7:08:47 PM UTC+10, Michael Hatherly wrote:

> Before this JuliaParser was at version v0.6.3, are you sure we should try 
> reverting to v0.1.2?
>
> See the tagged versions 
> https://github.com/jakebolewski/JuliaParser.jl/releases. So that’s the 
> next latest tagged version. You could probably checkout a specific commit 
> prior to the commit that’s causing the breakage instead though.
>
> What version of Jewel.jl and LightTable.jl are you using?
>
> — Mike
> ​
>
> On Sunday, 20 September 2015 10:56:22 UTC+2, Greg Plowman wrote:
>>
>> Hi,
>>
>> I tried Pkg.pin("JuliaParser", v"0.1.2") but now I get the following 
>> error (multiple times).
>>
>> Before this JuliaParser was at version v0.6.3, are you sure we should try 
>> reverting to v0.1.2?
>>
>>
>> WARNING: LightTable.jl: `skipws` has no method matching skipws(::
>> TokenStream)
>>  in scopes at C:\Users\Greg\.julia\v0.3\Jewel\src\parse\scope.jl:148
>>  in codemodule at C:\Users\Greg\.julia\v0.3\Jewel\src\parse/parse.jl:141
>>  in filemodule at C:\Users\Greg\.julia\v0.3\Jewel\src\module.jl:93
>>  in anonymous at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable\misc.jl:5
>>  in handlecmd at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/
>> LightTable.jl:65
>>  in handlenext at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/
>> LightTable.jl:81
>>  in server at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/LightTable.
>> jl:22
>>  in server at C:\Users\Greg\.julia\v0.3\Jewel\src\Jewel.jl:18
>>  in include at boot.jl:245
>>  in include_from_node1 at loading.jl:128
>>  in process_options at client.jl:285
>>  in _start at client.jl:354
>>
>>
>>
>> Any other suggestions?
>>
>> --Greg
>>
>>
>> On Sunday, September 20, 2015 at 6:16:10 PM UTC+10, Michael Hatherly 
>> wrote:
>>
>>> The type cannot be constructed error should be fixed on 0.3 by 
>>> https://github.com/jakebolewski/JuliaParser.jl/pull/25. In the mean 
>>> time you could Pkg.pin("JuliaParser", v"0.1.2") and see if that fixes 
>>> the problem on Julia 0.3. (Or a version earlier than v"0.1.2" if 
>>> needed.)
>>>
>>> I’ve come across the cannot resize array with shared data error a while 
>>> ago with the Atom-based Juno. It was fixed by Pkg.checkouting all the 
>>> involved packages. Might be the same for the LightTable-base Juno, worth a 
>>> try maybe.
>>>
>>> — Mike
>>> On Saturday, 19 September 2015 19:09:22 UTC+2, Serge Santos wrote:

 I tried to solve the problem by running Julia 0.4.0-rc2 instead of 
 Julia 0.3.11. I manage to execute a few commands in Juno, but juno/julia 
 is 
 stuck as before. The error message is slightly different though:


- 

WARNING: LightTable.jl: cannot resize array with shared data
 in push! at array.jl:430
 in read_operator at 
 C:\Users\Serge\.julia\v0.4\JuliaParser\src\lexer.jl:368
 in next_token at 
 C:\Users\Serge\.julia\v0.4\JuliaParser\src\lexer.jl:752
 in qualifiedname at 
 C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:59
 in nexttoken at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:78
 in nextscope! at 
 C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:116
 in scopes at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:149
 [inlined code] from C:\Users\Serge\.julia\v0.4\Lazy\src\macros.jl:141
 in codemodule at C:\Users\Serge\.julia\v0.4\Jewel\src\parse/parse.jl:8
 in getmodule at C:\Users\Serge\.julia\v0.4\Jewel\src\eval.jl:42
 in anonymous at 
 C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable\eval.jl:51
 in handlecmd at 
 C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:65
 in handlenext at 
 C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:81
 in server at 
 C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:22
 in server at C:\Users\Serge\.julia\v0.4\Jewel\src\Jewel.jl:18
 in include at boot.jl:261
 in include_from_node1 at loading.jl:304
 in process_options at client.jl:308
 in _start at client.jl:411



 On Saturday, 19 September 2015 10:40:49 UTC+1, JKPie wrote:
>
> I have the same problem, I have 

[julia-users] Re: Juno stopped working - error message

[Michael Hatherly]

I can’t see LightTable listed in Pkg.status() output in either PC

The LightTable module is part of the Jewel package is seems, 
https://github.com/one-more-minute/Jewel.jl/blob/fb854b0a64047ee642773c0aa824993714ee7f56/src/Jewel.jl#L22,
 
and so won’t show up on Pkg.status() output since it’s not a true package 
by itself. Apologies for the misleading directions there.

What other packages would Juno depend on?

You can manually walk through the REQUIRE files to see what Jewel depends 
on, or use MetadataTools to do it:

julia> using MetadataTools
julia> pkgmeta = get_all_pkg();
julia> graph = make_dep_graph(pkgmeta);
julia> deps = get_pkg_dep_graph("Jewel", graph);
julia> map(println, keys(deps.p_to_i));

You shouldn’t need to change versions for most, if any, of what’s listed 
though. (Don’t forget to call Pkg.free on each package you pin once newer 
versions of the packages are tagged.) Compat 0.7.1 should be far enough 
back I think.

— Mike
​
On Sunday, 20 September 2015 13:29:38 UTC+2, Greg Plowman wrote:
>
> OK I see that second latest tag is v0.1.2 (17 June 2014). Seems a strange 
> jump.
>
> But now I understand pinning, I can use a strategy of rolling back 
> Juno-related packages until Juno works again.
>
> What other packages would Juno depend on?
>
> To help me in this endeavour, I have access to another PC on which Juno 
> runs (almost) without error.
> Confusingly, Pkg.status() reports JuliaParser v0.6.2 on this second PC
> Jewel is v1.0.6 on both PCs.
> I can't see LightTable listed in Pkg.status() output in either PC
>
> I think Compat v0.7.2 is also causing ERROR: @doc not defined issue (
> https://groups.google.com/forum/#!topic/julia-users/rsM4hxdkAxg)
> so maybe reverting back to Compat v0.7.0 might also help.
>
> -- Greg
>
>
> On Sunday, September 20, 2015 at 7:08:47 PM UTC+10, Michael Hatherly wrote:
>
>> Before this JuliaParser was at version v0.6.3, are you sure we should try 
>> reverting to v0.1.2?
>>
>> See the tagged versions 
>> https://github.com/jakebolewski/JuliaParser.jl/releases. So that’s the 
>> next latest tagged version. You could probably checkout a specific commit 
>> prior to the commit that’s causing the breakage instead though.
>>
>> What version of Jewel.jl and LightTable.jl are you using?
>>
>> — Mike
>> ​
>>
>> On Sunday, 20 September 2015 10:56:22 UTC+2, Greg Plowman wrote:
>>>
>>> Hi,
>>>
>>> I tried Pkg.pin("JuliaParser", v"0.1.2") but now I get the following 
>>> error (multiple times).
>>>
>>> Before this JuliaParser was at version v0.6.3, are you sure we should 
>>> try reverting to v0.1.2?
>>>
>>>
>>> WARNING: LightTable.jl: `skipws` has no method matching skipws(::
>>> TokenStream)
>>>  in scopes at C:\Users\Greg\.julia\v0.3\Jewel\src\parse\scope.jl:148
>>>  in codemodule at C:\Users\Greg\.julia\v0.3\Jewel\src\parse/parse.jl:141
>>>  in filemodule at C:\Users\Greg\.julia\v0.3\Jewel\src\module.jl:93
>>>  in anonymous at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable\misc.jl:
>>> 5
>>>  in handlecmd at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/
>>> LightTable.jl:65
>>>  in handlenext at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/
>>> LightTable.jl:81
>>>  in server at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/LightTable.
>>> jl:22
>>>  in server at C:\Users\Greg\.julia\v0.3\Jewel\src\Jewel.jl:18
>>>  in include at boot.jl:245
>>>  in include_from_node1 at loading.jl:128
>>>  in process_options at client.jl:285
>>>  in _start at client.jl:354
>>>
>>>
>>>
>>> Any other suggestions?
>>>
>>> --Greg
>>>
>>>
>>> On Sunday, September 20, 2015 at 6:16:10 PM UTC+10, Michael Hatherly 
>>> wrote:
>>>
 The type cannot be constructed error should be fixed on 0.3 by 
 https://github.com/jakebolewski/JuliaParser.jl/pull/25. In the mean 
 time you could Pkg.pin("JuliaParser", v"0.1.2") and see if that fixes 
 the problem on Julia 0.3. (Or a version earlier than v"0.1.2" if 
 needed.)

 I’ve come across the cannot resize array with shared data error a 
 while ago with the Atom-based Juno. It was fixed by Pkg.checkouting 
 all the involved packages. Might be the same for the LightTable-base Juno, 
 worth a try maybe.

 — Mike
 On Saturday, 19 September 2015 19:09:22 UTC+2, Serge Santos wrote:
>
> I tried to solve the problem by running Julia 0.4.0-rc2 instead of 
> Julia 0.3.11. I manage to execute a few commands in Juno, but juno/julia 
> is 
> stuck as before. The error message is slightly different though:
>
>
>- 
>
>WARNING: LightTable.jl: cannot resize array with shared data
> in push! at array.jl:430
> in read_operator at 
> C:\Users\Serge\.julia\v0.4\JuliaParser\src\lexer.jl:368
> in next_token at 
> C:\Users\Serge\.julia\v0.4\JuliaParser\src\lexer.jl:752
> in qualifiedname at 
> C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:59
> in nexttoken at 

[julia-users] Re: Juno stopped working - error message

[Dongning Guo]

In case you're stuck, this may be a way out:
I installed Atom editor and it seems Julia (v0.5??? nightly build)
works with it after installing a few packages.  I'm learning to use
the new environment ...
See https://github.com/JunoLab/atom-julia-client/tree/master/manual


On Sunday, September 20, 2015 at 6:59:02 AM UTC-5, Michael Hatherly wrote:
>
> I can’t see LightTable listed in Pkg.status() output in either PC
>
> The LightTable module is part of the Jewel package is seems, 
> https://github.com/one-more-minute/Jewel.jl/blob/fb854b0a64047ee642773c0aa824993714ee7f56/src/Jewel.jl#L22,
>  
> and so won’t show up on Pkg.status() output since it’s not a true package 
> by itself. Apologies for the misleading directions there.
>
> What other packages would Juno depend on?
>
> You can manually walk through the REQUIRE files to see what Jewel depends 
> on, or use MetadataTools to do it:
>
> julia> using MetadataTools
> julia> pkgmeta = get_all_pkg();
> julia> graph = make_dep_graph(pkgmeta);
> julia> deps = get_pkg_dep_graph("Jewel", graph);
> julia> map(println, keys(deps.p_to_i));
>
> You shouldn’t need to change versions for most, if any, of what’s listed 
> though. (Don’t forget to call Pkg.free on each package you pin once newer 
> versions of the packages are tagged.) Compat 0.7.1 should be far enough 
> back I think.
>
> — Mike
> ​
> On Sunday, 20 September 2015 13:29:38 UTC+2, Greg Plowman wrote:
>>
>> OK I see that second latest tag is v0.1.2 (17 June 2014). Seems a strange 
>> jump.
>>
>> But now I understand pinning, I can use a strategy of rolling back 
>> Juno-related packages until Juno works again.
>>
>> What other packages would Juno depend on?
>>
>> To help me in this endeavour, I have access to another PC on which Juno 
>> runs (almost) without error.
>> Confusingly, Pkg.status() reports JuliaParser v0.6.2 on this second PC
>> Jewel is v1.0.6 on both PCs.
>> I can't see LightTable listed in Pkg.status() output in either PC
>>
>> I think Compat v0.7.2 is also causing ERROR: @doc not defined issue (
>> https://groups.google.com/forum/#!topic/julia-users/rsM4hxdkAxg)
>> so maybe reverting back to Compat v0.7.0 might also help.
>>
>> -- Greg
>>
>>
>> On Sunday, September 20, 2015 at 7:08:47 PM UTC+10, Michael Hatherly 
>> wrote:
>>
>>> Before this JuliaParser was at version v0.6.3, are you sure we should 
>>> try reverting to v0.1.2?
>>>
>>> See the tagged versions 
>>> https://github.com/jakebolewski/JuliaParser.jl/releases. So that’s the 
>>> next latest tagged version. You could probably checkout a specific commit 
>>> prior to the commit that’s causing the breakage instead though.
>>>
>>> What version of Jewel.jl and LightTable.jl are you using?
>>>
>>> — Mike
>>> ​
>>>
>>> On Sunday, 20 September 2015 10:56:22 UTC+2, Greg Plowman wrote:

 Hi,

 I tried Pkg.pin("JuliaParser", v"0.1.2") but now I get the following 
 error (multiple times).

 Before this JuliaParser was at version v0.6.3, are you sure we should 
 try reverting to v0.1.2?


 WARNING: LightTable.jl: `skipws` has no method matching skipws(::
 TokenStream)
  in scopes at C:\Users\Greg\.julia\v0.3\Jewel\src\parse\scope.jl:148
  in codemodule at C:\Users\Greg\.julia\v0.3\Jewel\src\parse/parse.jl:
 141
  in filemodule at C:\Users\Greg\.julia\v0.3\Jewel\src\module.jl:93
  in anonymous at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable\misc.jl
 :5
  in handlecmd at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/
 LightTable.jl:65
  in handlenext at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/
 LightTable.jl:81
  in server at C:\Users\Greg\.julia\v0.3\Jewel\src\LightTable/LightTable
 .jl:22
  in server at C:\Users\Greg\.julia\v0.3\Jewel\src\Jewel.jl:18
  in include at boot.jl:245
  in include_from_node1 at loading.jl:128
  in process_options at client.jl:285
  in _start at client.jl:354



 Any other suggestions?

 --Greg


 On Sunday, September 20, 2015 at 6:16:10 PM UTC+10, Michael Hatherly 
 wrote:

> The type cannot be constructed error should be fixed on 0.3 by 
> https://github.com/jakebolewski/JuliaParser.jl/pull/25. In the mean 
> time you could Pkg.pin("JuliaParser", v"0.1.2") and see if that fixes 
> the problem on Julia 0.3. (Or a version earlier than v"0.1.2" if 
> needed.)
>
> I’ve come across the cannot resize array with shared data error a 
> while ago with the Atom-based Juno. It was fixed by Pkg.checkouting 
> all the involved packages. Might be the same for the LightTable-base 
> Juno, 
> worth a try maybe.
>
> — Mike
> On Saturday, 19 September 2015 19:09:22 UTC+2, Serge Santos wrote:
>>
>> I tried to solve the problem by running Julia 0.4.0-rc2 instead of 
>> Julia 0.3.11. I manage to execute a few commands in Juno, but juno/julia 
>> is 
>> stuck as before. The error message is 

[julia-users] Re: Juno stopped working - error message

[Serge Santos]

This is working! I rolled back and pinned all packages with different 
version numbers and Juno runs again. Thank you so much, Greg, Very much 
appreciated.

On Monday, 21 September 2015 02:09:56 UTC+1, Greg Plowman wrote:
>
> Serge,
>
> Below is output of Pkg.status():
>
> I had previously tried removing many packages, but nothing is pinned (so 
> not sure if rolling back will result in same config)
>
> The only error message I receive using Juno is:
> symbol could not be found jl_generating_output (-1): The specified 
> procedure could not be found.
>
> but after this everything seems to work as normal.
>
> Hope this helps.
> -- Greg
>
>
>_
>_   _ _(_)_ |  A fresh approach to technical computing
>   (_) | (_) (_)|  Documentation: http://docs.julialang.org
>_ _   _| |_  __ _   |  Type "help()" for help.
>   | | | | | | |/ _` |  |
>   | | |_| | | | (_| |  |  Version 0.3.11 (2015-07-27 06:18 UTC)
>  _/ |\__'_|_|_|\__'_|  |  Official http://julialang.org/ release
> |__/   |  x86_64-w64-mingw32
> julia> Pkg.status()
> 9 required packages:
>  - Dates 0.3.2
>  - Distributions 0.8.6
>  - HDF5  0.5.5
>  - ImageView 0.1.16
>  - Images0.4.47
>  - JLD   0.5.4
>  - Jewel 1.0.6
>  - Optim 0.4.2
>  - ZMQ   0.2.0
> 39 additional packages:
>  - ArrayViews0.6.3
>  - BinDeps   0.3.15
>  - Blosc 0.1.4
>  - Cairo 0.2.30
>  - Calculus  0.1.10
>  - ColorTypes0.1.4
>  - ColorVectorSpace  0.0.3
>  - Colors0.5.3
>  - Compat0.7.1
>  - Compose   0.3.15
>  - DataStructures0.3.12
>  - Docile0.5.18
>  - DualNumbers   0.1.3
>  - FactCheck 0.4.0
>  - FixedPointNumbers 0.0.10
>  - Graphics  0.1.0
>  - HttpCommon0.1.2
>  - IniFile   0.2.4
>  - Iterators 0.1.8
>  - JSON  0.4.5
>  - JuliaParser   0.6.2
>  - LNR   0.0.1
>  - Lazy  0.10.0
>  - LibExpat  0.0.8
>  - MacroTools0.2.0
>  - NaNMath   0.1.0
>  - PDMats0.3.5
>  - Reexport  0.0.3
>  - Requires  0.2.0
>  - SHA   0.1.1
>  - SIUnits   0.0.5
>  - StatsBase 0.7.2
>  - StatsFuns 0.1.3
>  - TexExtensions 0.0.2
>  - Tk0.3.6
>  - URIParser 0.0.7
>  - WinRPM0.1.12
>  - Winston   0.11.12
>  - Zlib  0.1.9
> Julia>
>
>
>
> On Monday, September 21, 2015 at 9:44:24 AM UTC+10, Serge Santos wrote:
>
> Hi All,
>
> I tried to roll back to JuliaParser v0.6.2 and it didn't work. 
>
> If someone still manages to successfully run Juno with Julia 0.3.11, can 
> you please send the list of packages with version numbers that does not 
> create any issues with Juno (i.e,, output from Pkg.status()). I was not 
> able to figure out what combination of versions work. 
>
> Many thanks in advance
> Serge
>
> On Monday, 21 September 2015 00:16:27 UTC+1, Greg Plowman wrote:
>
> Hi All,
>
> On 2 different PCs where Juno works (almost without error) Pkg.status() 
> reports JuliaParser v0.6.2
> On PC that has Juno errors, Pkg.status() reports JuliaParser v0.6.3
> Rolling back to JuliaParser v0.1.2 creates different errors.
> So it seems we need to revert to JuliaParser v0.6.2
>
> I'm not at a PC where I can see if we can pin v0.6.2, in light of the 
> following:
>
> Before this JuliaParser was at version v0.6.3, are you sure we should try 
> reverting to v0.1.2?
>
> See the tagged versions 
>
> https://github.com/jakebolewski/JuliaParser.jl/releases. So that’s the 
> next latest tagged version. You could probably checkout a specific commit 
> prior to the commit that’s causing the breakage instead though.
>
> Also, I don't want to play around with Pkg.ANYTHING on a working 
> configuration at the moment :)
>
> -- Greg
>
>
> On Monday, September 21, 2015 at 4:50:37 AM UTC+10, Tony Kelman wrote:
>
> What's temporarily broken here is some of the packages that 
> Light-Table-based Juno relies on to work. In the meantime you can still use 
> command-line REPL Julia, and while it's not the most friendly interface 
> your code will still run. Your estimation of the Julia ecosystem's 
> robustness is pretty accurate though, if you really want to ensure things 
> stay working the 

[julia-users] Re: Juno stopped working - error message

[Serge Santos]

Thank you all for your inputs. It tried your suggestions and, 
unfortunately, it does not work. I tried Atom but, after a good start and 
some success, it keeps crashing in middle of a calculation (windows 10).

To summarize what I tried with Juno and julia 0.3.11:
- Compat v.0.7.0 (pinned)
- JuliaParser V0.1.2  (pinned)
- Jewel v1.0.6.

I get a first error message, which seems to indicate that Julia cannot 
generate an output.

*symbol could not be found jl_generating_output (-1): The specified 
procedure could not be found.*

Followed by:

*WARNING: LightTable.jl: `skipws` has no method matching 
skipws(::TokenStream)*
* in scopes at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:148*
* in codemodule at C:\Users\Serge\.julia\v0.3\Jewel\src\parse/parse.jl:141*
* in getmodule at C:\Users\Serge\.julia\v0.3\Jewel\src\eval.jl:42*
* in anonymous at 
C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable\eval.jl:51*
* in handlecmd at 
C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:65*
* in handlenext at 
C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:81*
* in server at 
C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:22*
* in server at C:\Users\Serge\.julia\v0.3\Jewel\src\Jewel.jl:18*
* in include at boot.jl:245*
* in include_from_node1 at loading.jl:128*
* in process_options at client.jl:285*
* in _start at client.jl:354*

Looking at dependencies with MetadataTools, I smply got:* nothing.* I 
assume that Jewel does not have any dependencies.

I have a lot of understanding for the effort that goes into making the 
Julia project work and a success, but I just lost two days of my life 
trying to make things work and I have an important deadline ahead that I am 
likely to miss because I relied on a promising tool that, unfortunately, 
does not seem robust enough at this stage given the amount of development 
happening.It makes me wonder if I should not wait until Julia becomes more 
established and robust and switch to other solutions.

On Sunday, 20 September 2015 16:47:05 UTC+1, Dongning Guo wrote:
>
> In case you're stuck, this may be a way out:
> I installed Atom editor and it seems Julia (v0.5??? nightly build)
> works with it after installing a few packages.  I'm learning to use
> the new environment ...
> See https://github.com/JunoLab/atom-julia-client/tree/master/manual
>
>
> On Sunday, September 20, 2015 at 6:59:02 AM UTC-5, Michael Hatherly wrote:
>>
>> I can’t see LightTable listed in Pkg.status() output in either PC
>>
>> The LightTable module is part of the Jewel package is seems, 
>> https://github.com/one-more-minute/Jewel.jl/blob/fb854b0a64047ee642773c0aa824993714ee7f56/src/Jewel.jl#L22,
>>  
>> and so won’t show up on Pkg.status() output since it’s not a true 
>> package by itself. Apologies for the misleading directions there.
>>
>> What other packages would Juno depend on?
>>
>> You can manually walk through the REQUIRE files to see what Jewel depends 
>> on, or use MetadataTools to do it:
>>
>> julia> using MetadataTools
>> julia> pkgmeta = get_all_pkg();
>> julia> graph = make_dep_graph(pkgmeta);
>> julia> deps = get_pkg_dep_graph("Jewel", graph);
>> julia> map(println, keys(deps.p_to_i));
>>
>> You shouldn’t need to change versions for most, if any, of what’s listed 
>> though. (Don’t forget to call Pkg.free on each package you pin once 
>> newer versions of the packages are tagged.) Compat 0.7.1 should be far 
>> enough back I think.
>>
>> — Mike
>> ​
>> On Sunday, 20 September 2015 13:29:38 UTC+2, Greg Plowman wrote:
>>>
>>> OK I see that second latest tag is v0.1.2 (17 June 2014). Seems a 
>>> strange jump.
>>>
>>> But now I understand pinning, I can use a strategy of rolling back 
>>> Juno-related packages until Juno works again.
>>>
>>> What other packages would Juno depend on?
>>>
>>> To help me in this endeavour, I have access to another PC on which Juno 
>>> runs (almost) without error.
>>> Confusingly, Pkg.status() reports JuliaParser v0.6.2 on this second PC
>>> Jewel is v1.0.6 on both PCs.
>>> I can't see LightTable listed in Pkg.status() output in either PC
>>>
>>> I think Compat v0.7.2 is also causing ERROR: @doc not defined issue (
>>> https://groups.google.com/forum/#!topic/julia-users/rsM4hxdkAxg)
>>> so maybe reverting back to Compat v0.7.0 might also help.
>>>
>>> -- Greg
>>>
>>>
>>> On Sunday, September 20, 2015 at 7:08:47 PM UTC+10, Michael Hatherly 
>>> wrote:
>>>
 Before this JuliaParser was at version v0.6.3, are you sure we should 
 try reverting to v0.1.2?

 See the tagged versions 
 https://github.com/jakebolewski/JuliaParser.jl/releases. So that’s the 
 next latest tagged version. You could probably checkout a specific commit 
 prior to the commit that’s causing the breakage instead though.

 What version of Jewel.jl and LightTable.jl are you using?

 — Mike
 ​

 On Sunday, 20 September 2015 10:56:22 UTC+2, Greg Plowman wrote:
>
> Hi,
>
> I tried 

[julia-users] Re: Juno stopped working - error message

[Eric Forgy]

Reading this thread hurts. I imagine the frustration.

I'm still mostly an observer, but as an observer, I see the guys behind the 
scenes with the skills to address these issues are working super hard to 
get Juno/Atom (Juno2) at feature parity with the prior Juno. At that point, 
support for the old Juno will probably drop to almost nothing because 
attention and limited resources will be focused on Juno2 (which may already 
be the case).

I've asked my developers to switch to Julio 0.4 RC1 and Juno2. Although it 
might be a little unpolished at the moment, I think this is one small way 
we can contribute back, i.e. supporting the new path and reporting issues 
(fixing them if we can).

With the pace of development I see on Github, I expect Juno2 will be the 
way to go very soon.

Serge, you mentioned you had some problems with 
Pkg.checkout("JuliaParser"), which is keeping you from using Juno2. What 
was the problem? You might consider filing an issue 
 or pursuing it 
here. It is probably worth the effort to get Juno2 to work.

Good luck! Wish I could help more.

[julia-users] Re: Juno stopped working - error message

[JKPie]

I have the same problem, I have spent couple of hours reinstalling Julia 
and Juno on Windows and Linux with no result. The code works fine, when I 
call it from command line directly. 
Please help it is freezing my work :/
J

[julia-users] Re: Juno stopped working - error message

[Serge Santos]

I tried to solve the problem by running Julia 0.4.0-rc2 instead of Julia 
0.3.11. I manage to execute a few commands in Juno, but juno/julia is stuck 
as before. The error message is slightly different though:


   - 
   
   WARNING: LightTable.jl: cannot resize array with shared data
in push! at array.jl:430
in read_operator at C:\Users\Serge\.julia\v0.4\JuliaParser\src\lexer.jl:368
in next_token at C:\Users\Serge\.julia\v0.4\JuliaParser\src\lexer.jl:752
in qualifiedname at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:59
in nexttoken at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:78
in nextscope! at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:116
in scopes at C:\Users\Serge\.julia\v0.4\Jewel\src\parse\scope.jl:149
[inlined code] from C:\Users\Serge\.julia\v0.4\Lazy\src\macros.jl:141
in codemodule at C:\Users\Serge\.julia\v0.4\Jewel\src\parse/parse.jl:8
in getmodule at C:\Users\Serge\.julia\v0.4\Jewel\src\eval.jl:42
in anonymous at C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable\eval.jl:51
in handlecmd at 
C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:65
in handlenext at 
C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:81
in server at 
C:\Users\Serge\.julia\v0.4\Jewel\src\LightTable/LightTable.jl:22
in server at C:\Users\Serge\.julia\v0.4\Jewel\src\Jewel.jl:18
in include at boot.jl:261
in include_from_node1 at loading.jl:304
in process_options at client.jl:308
in _start at client.jl:411
   
   

On Saturday, 19 September 2015 10:40:49 UTC+1, JKPie wrote:
>
> I have the same problem, I have spent couple of hours reinstalling Julia 
> and Juno on Windows and Linux with no result. The code works fine, when I 
> call it from command line directly. 
> Please help it is freezing my work :/
> J
>

[julia-users] Re: Juno stopped working - error message

[Dongning Guo]

My Juno stopped working too.  Looks like I'm seeing the same error 
messages.  It didn't help to reinstall the latest bundle or a previous 
version I had (which worked fine before).  Tried a few things but nothing 
worked.

On Friday, September 18, 2015 at 5:38:16 PM UTC-5, Serge Santos wrote:
>
> Thank you, Nils. I tried Pkg.checkout("JuliaParser"), but it didn't work. 
> Very much appreciate if you have another idea. 
>
> I will try with JunoAtom in the hope to be able to continue working. 
>
> On Friday, 18 September 2015 20:42:33 UTC+1, Nils Gudat wrote:
>>
>> I'd say just switch to JunoAtom, it's much nicer :)
>>
>> But in all seriousness, these "utf8sizeof" related bugs can often be 
>> solved by doing Pkg.checkout("JuliaParser")
>>
>

[julia-users] Re: Juno stopped working - error message

[Serge Santos]

Thank you, Nils. I tried Pkg.checkout("JuliaParser"), but it didn't work. 
Very much appreciate if you have another idea. 

I will try with JunoAtom in the hope to be able to continue working. 

On Friday, 18 September 2015 20:42:33 UTC+1, Nils Gudat wrote:
>
> I'd say just switch to JunoAtom, it's much nicer :)
>
> But in all seriousness, these "utf8sizeof" related bugs can often be 
> solved by doing Pkg.checkout("JuliaParser")
>

[julia-users] Re: Juno stopped working - error message

[Nils Gudat]

I'd say just switch to JunoAtom, it's much nicer :)

But in all seriousness, these "utf8sizeof" related bugs can often be solved 
by doing Pkg.checkout("JuliaParser")

[julia-users] Re: Juno stopped working - error message

[Serge Santos]

I also tried on my iMac (currently on Windows) and it does not work either. 
Both installations are independent. The error message is:

WARNING: LightTable.jl: type cannot be constructed
 in utf8sizeof at C:\Users\Serge\.julia\v0.3\JuliaParser\src\lexer.jl:322
 in skip_to_eol at C:\Users\Serge\.julia\v0.3\JuliaParser\src\lexer.jl:349
 in lexcomment at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:27
 in nexttoken at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:74
 in nextscope! at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:116
 in scopes at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:149
 in codemodule at C:\Users\Serge\.julia\v0.3\Jewel\src\parse/parse.jl:141
 in filemodule at C:\Users\Serge\.julia\v0.3\Jewel\src\module.jl:93
 in anonymous at C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable\misc.jl:5
 in handlecmd at 
C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:65
 in handlenext at 
C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:81
 in server at C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:22
 in server at C:\Users\Serge\.julia\v0.3\Jewel\src\Jewel.jl:18
 in include at boot.jl:245
 in include_from_node1 at loading.jl:128
 in process_options at client.jl:285
 in _start at client.jl:354



On Friday, 18 September 2015 17:35:56 UTC+1, Serge Santos wrote:
>
> Hi,
>
> Juno was working fine, but I had to restart Juno and now it keeps churning 
> after successfully connecting with Julia but I cannot use the shell to work 
> (nothing happen). There are no reasons why it should not work anymore.
>
> All the Julia packages are updated and up-to-date and I even reinstalled 
> Julia and Juno. It has not changed anything. 
>
> Any help / advise is highly appreciated (it is quite frustrating).
>
> Here is the error message:
>
>
>- 
>
>WARNING: LightTable.jl: type cannot be constructed
> in utf8sizeof at C:\Users\Serge\.julia\v0.3\JuliaParser\src\lexer.jl:322
> in skip_to_eol at C:\Users\Serge\.julia\v0.3\JuliaParser\src\lexer.jl:349
> in lexcomment at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:27
> in nexttoken at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:74
> in nextscope! at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:116
> in scopes at C:\Users\Serge\.julia\v0.3\Jewel\src\parse\scope.jl:149
> in codemodule at C:\Users\Serge\.julia\v0.3\Jewel\src\parse/parse.jl:141
> in filemodule at C:\Users\Serge\.julia\v0.3\Jewel\src\module.jl:93
> in anonymous at C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable\misc.jl:5
> in handlecmd at 
> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:65
> in handlenext at 
> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:81
> in server at 
> C:\Users\Serge\.julia\v0.3\Jewel\src\LightTable/LightTable.jl:22
> in server at C:\Users\Serge\.julia\v0.3\Jewel\src\Jewel.jl:18
> in include at boot.jl:245
> in include_from_node1 at loading.jl:128
> in process_options at client.jl:285
> in _start at client.jl:354
>
>- 
>
>symbol could not be found jl_generating_output (-1): The specified 
> procedure could not be found.
>
>
>- 
>
>Invalid behavior: :lt.objs.clients.tcp/send!
>
>- 
>
>Error: This socket has been ended by the other party
>at Socket.writeAfterFIN [as write] (net.js:275:12)
>at lt.objs.clients.tcp.send_to 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:32857:96)
>at Function.lt.objs.clients.tcp.__BEH__send_BANG_ 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:32937:38)
>at c 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:6196:14)
>at a 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:6236:18)
>at c 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:20443:76)
>at a 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:20477:18)
>at a 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:20488:34)
>at b 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:20492:14)
>at Function.lt.objs.clients.__BEH__try_send 
> (file:///C:/Users/Serge/AppData/Local/juno-windows-x64/resources/app/core/node_modules/lighttable/bootstrap.js:28855:189)
>
>
>