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

Cannot load LazySets and Ipopt simulatneously when Revise is active #3040

Closed
lassepe opened this issue Aug 18, 2022 · 2 comments · Fixed by #3042
Closed

Cannot load LazySets and Ipopt simulatneously when Revise is active #3040

lassepe opened this issue Aug 18, 2022 · 2 comments · Fixed by #3042
Labels
external 📤 Related to external packages fix 🤕 Fix to a problem that is not too serious

Comments

@lassepe
Copy link
Contributor

lassepe commented Aug 18, 2022

When Revise.jl is loaded I cannot load LazySets and Ipopt at the same time.

Reproducer (both in Julia 1.7.3 and 1.8.0):

] activate --temp
using Revise, LazySets, Ipopt

Results in the following error:

┌ Error: Error during package callback
│   exception =1-element ExceptionStack:
│    MethodError: no method matching add_require(::String, ::Module, ::String, ::String, ::Symbol)
│    Closest candidates are:add_require(::String, ::Module, ::String, ::String, ::Expr) at ~/.julia/packages/Revise/do2nH/src/pkgs.jl:183
│    Stacktrace:
│      [1] withnotifications(::Any, ::Vararg{Any})
│        @ Requires ~/.julia/packages/Requires/Z8rfN/src/require.jl:70
│      [2] (::LazySets.var"#462#501")()
│        @ LazySets ~/.julia/packages/Requires/Z8rfN/src/require.jl:106
│      [3] #invokelatest#2
│        @ ./essentials.jl:729 [inlined]
│      [4] invokelatest
│        @ ./essentials.jl:726 [inlined]
│      [5] foreach
│        @ ./abstractarray.jl:2774 [inlined]
│      [6] loadpkg(pkg::Base.PkgId)
│        @ Requires ~/.julia/packages/Requires/Z8rfN/src/require.jl:27
│      [7] #invokelatest#2
│        @ ./essentials.jl:729 [inlined]
│      [8] invokelatest
│        @ ./essentials.jl:726 [inlined]
│      [9] run_package_callbacks(modkey::Base.PkgId)
│        @ Base ./loading.jl:869
│     [10] _require_prelocked(uuidkey::Base.PkgId)
│        @ Base ./loading.jl:1206
│     [11] macro expansion
│        @ ./loading.jl:1180 [inlined]
│     [12] macro expansion
│        @ ./lock.jl:223 [inlined]
│     [13] require(into::Module, mod::Symbol)
│        @ Base ./loading.jl:1144
│     [14] top-level scope
│        @ ~/.julia/packages/Infiltrator/qHXTS/src/Infiltrator.jl:680
│     [15] eval
│        @ ./boot.jl:368 [inlined]
│     [16] eval_user_input(ast::Any, backend::REPL.REPLBackend)
│        @ REPL ~/.julia/juliaup/julia-1.8.0+0.x64/share/julia/stdlib/v1.8/REPL/src/REPL.jl:151
│     [17] repl_backend_loop(backend::REPL.REPLBackend)
│        @ REPL ~/.julia/juliaup/julia-1.8.0+0.x64/share/julia/stdlib/v1.8/REPL/src/REPL.jl:247
│     [18] start_repl_backend(backend::REPL.REPLBackend, consumer::Any)
│        @ REPL ~/.julia/juliaup/julia-1.8.0+0.x64/share/julia/stdlib/v1.8/REPL/src/REPL.jl:232
│     [19] run_repl(repl::REPL.AbstractREPL, consumer::Any; backend_on_current_task::Bool)
│        @ REPL ~/.julia/juliaup/julia-1.8.0+0.x64/share/julia/stdlib/v1.8/REPL/src/REPL.jl:369
│     [20] run_repl(repl::REPL.AbstractREPL, consumer::Any)
│        @ REPL ~/.julia/juliaup/julia-1.8.0+0.x64/share/julia/stdlib/v1.8/REPL/src/REPL.jl:355
│     [21] (::Base.var"#966#968"{Bool, Bool, Bool})(REPL::Module)
│        @ Base ./client.jl:419
│     [22] #invokelatest#2
│        @ ./essentials.jl:729 [inlined]
│     [23] invokelatest
│        @ ./essentials.jl:726 [inlined]
│     [24] run_main_repl(interactive::Bool, quiet::Bool, banner::Bool, history_file::Bool, color_set::Bool)
│        @ Base ./client.jl:404
│     [25] exec_options(opts::Base.JLOptions)
│        @ Base ./client.jl:318
│     [26] _start()
│        @ Base ./client.jl:522
└ @ Base loading.jl:874

I'm not sure whether this is a bug of LazySets, Revise, or Require.

@lassepe
Copy link
Contributor Author

lassepe commented Aug 18, 2022

cc @timholy

@schillic schillic added fix 🤕 Fix to a problem that is not too serious external 📤 Related to external packages labels Aug 18, 2022
@schillic
Copy link
Member

I can confirm, but I do not know what to do about it. This is the first time I see this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external 📤 Related to external packages fix 🤕 Fix to a problem that is not too serious
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants