We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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
The text was updated successfully, but these errors were encountered:
Config: don't assume error has msg field
a97f964
Fixes #570
4c549ac
Fixes #570 Also includes a stacktrace to startup.jl. Co-authored-by: Sebastian Pfitzner <[email protected]>
Config: don't assume error has msg field (#571)
5c7a2c6
Successfully merging a pull request may close this issue.
The docs recommend
for a robust setup, but on master
The text was updated successfully, but these errors were encountered: