Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@warn(e.msg) in the recommended config fails #570

Closed
tpapp opened this issue Nov 14, 2020 · 0 comments · Fixed by #571
Closed

@warn(e.msg) in the recommended config fails #570

tpapp opened this issue Nov 14, 2020 · 0 comments · Fixed by #571

Comments

@tpapp
Copy link
Contributor

tpapp commented Nov 14, 2020

The docs recommend

try
    using Revise
catch e
    @warn(e.msg)
end

for a robust setup, but on master

┌ Error: Exception while generating log record in module Main at /home/tamas/.julia/config/startup.jl:6
│   exception =
│    type InitError has no field msg
│    Stacktrace:
│     [1] getproperty(x::InitError, f::Symbol)
│       @ Base ./Base.jl:33
│     [2] macro expansion
│       @ logging.jl:340 [inlined]
│     [3] top-level scope
│       @ ~/.julia/config/startup.jl:6
│     [4] include
│       @ ./Base.jl:386 [inlined]
│     [5] include_ifexists
│       @ ./client.jl:202 [inlined]
│     [6] load_julia_startup()
│       @ Base ./client.jl:317
│     [7] exec_options(opts::Base.JLOptions)
│       @ Base ./client.jl:256
│     [8] _start()
│       @ Base ./client.jl:485
└ @ Main ~/.julia/config/startup.jl:6
timholy added a commit that referenced this issue Nov 14, 2020
timholy added a commit that referenced this issue Nov 14, 2020
Fixes #570
Also includes a stacktrace to startup.jl.

Co-authored-by: Sebastian Pfitzner <[email protected]>
timholy added a commit that referenced this issue Nov 15, 2020
Fixes #570
Also includes a stacktrace to startup.jl.

Co-authored-by: Sebastian Pfitzner <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant