FS#59735 - [julia] Weird behaviour with errors in Atom/Juno

Attached to Project: Community Packages
Opened by Lukas Hupe (lhupe) - Tuesday, 21 August 2018, 13:10 GMT
Last edited by Alexander F. Rødseth (xyproto) - Monday, 03 September 2018, 11:17 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Alexander F. Rødseth (xyproto)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

When using the julia binaries provided in this package, there are some problems
with error messages in the Juno IDE
I have already discussed this problem at the official julia discourse forum, see
https://discourse.julialang.org/t/error-handling-in-juno

Since they only occur when using the Arch package (instead of the official
julialang.org builds), I suppose the bug must have something to do with the build.

Additional info:
* on julia-2:1.0.0-1


Steps to reproduce:
* Install `atom`, then use its package manager to install the `uber-juno` package, restart atom
* create a new Julia source file, add the line `throw(ErrorException("foo"))`
* go to the line and run it by pressing Shift+Enter
* observe that the error message popup does not show the expected error message "foo", but rather a
weird, low-level error
This task depends upon

Closed by  Alexander F. Rødseth (xyproto)
Monday, 03 September 2018, 11:17 GMT
Reason for closing:  Upstream
Comment by Lukas Hupe (lhupe) - Tuesday, 21 August 2018, 14:23 GMT
Things have changed a little with the discovery of a bug in the Juno IDE – see the discourse thread
https://discourse.julialang.org/t/error-handling-in-juno/13757/11
for that

There is still a significant difference in the way the Arch binaries and the official julialang.org build handle the example case – errors are much more verbose using the Arch binaries.

However, since this doesn't actually seem to be "wrong" behaviour, I'm not sure whether this should stay open.
Comment by Alexander F. Rødseth (xyproto) - Monday, 27 August 2018, 11:15 GMT
Thanks for reporting, I can reproduce the problem. I get:

ERROR: LoadError: foo
Stacktrace:
[1] top-level scope at none:0
[2] (::getfield(Atom, Symbol("##120#124")){String,String,Module})() at /home/alexander/.julia/packages/Atom/jodeb/src/eval.jl:120
[3] withpath(::getfield(Atom, Symbol("##120#124")){String,String,Module}, ::Nothing) at /home/alexander/.julia/packages/CodeTools/8CjYJ/src/utils.jl:30
[4] withpath at /home/alexander/.julia/packages/Atom/jodeb/src/eval.jl:46 [inlined]
[5] #119 at /home/alexander/.julia/packages/Atom/jodeb/src/eval.jl:117 [inlined]
[6] hideprompt(::getfield(Atom, Symbol("##119#123")){String,String,Module}) at /home/alexander/.julia/packages/Atom/jodeb/src/repl.jl:76
[7] macro expansion at /home/alexander/.julia/packages/Atom/jodeb/src/eval.jl:116 [inlined]
[8] (::getfield(Atom, Symbol("##118#122")){Dict{String,Any}})() at ./task.jl:85
in expression starting at untitled-bb630592303f32a06c33f0a341184abe:1

The julia package does not use system libraries for many dependencies, since they don't work with Julia. They have a pretty "special" build setup, with many vendored dependencies.

Unless you can see something wrong in the Julia PKGBUILD (https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/julia), please report this upstream to the Julia devlopers (or to the atom plugin developers?), instead.

Loading...