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 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 >>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>
