-
Notifications
You must be signed in to change notification settings - Fork 111
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
Error revising: No method matching a functor created by JLLWrappers #706
Comments
This may be a naming inconsistency, i.e., an instance of gensymmed names changing because Revise has to re-parse the source code. AFAICT the true fix is to move pieces of Revise into Base, but that's still a bit in the future. |
I'm not sure if this is reproducible enough, but I find (at least part of) the issue is caused when the **UNSTAGING**
julia> WARNING: redefinition of constant libpng_jll.PATH. This may fail, cause incorrect answers, or produce other errors.
WARNING: redefinition of constant libpng_jll.LIBPATH. This may fail, cause incorrect answers, or produce other errors.
WARNING: redefinition of constant libpng_jll.PATH_list. This may fail, cause incorrect answers, or produce other errors.
WARNING: redefinition of constant libpng_jll.LIBPATH_list. This may fail, cause incorrect answers, or produce other errors.
┌ Error: Error watching manifest
│ exception =
│ MethodError: no method matching (::libpng_jll.var"#make_wrapper_dict#8"{libpng_jll.var"#parse_wrapper_platform#7"})(::String, ::Vector{String})
│ The function `make_wrapper_dict` exists, but no method is defined for this combination of argument types.
│ Stacktrace:
│ [1] top-level scope
│ @ ~/.julia/packages/JLLWrappers/GfYNv/src/toplevel_generators.jl:167
│ Revise evaluation error at /Users/user/.julia/packages/JLLWrappers/GfYNv/src/toplevel_generators.jl:167
│
│ Stacktrace:
│ [1] methods_by_execution!(recurse::Any, methodinfo::Revise.CodeTrackingMethodInfo, docexprs::Dict{Module, Vector{Expr}}, mod::Module, ex::Expr; mode::Symbol, disablebp::Bool, always_rethrow::Bool, kwargs::@Kwargs{})
│ @ Revise ~/.julia/packages/Revise/tTIBp/src/lowered.jl:296
└ @ Revise ~/.julia/packages/Revise/tTIBp/src/pkgs.jl:498
**STAGING**
WARNING: redefinition of constant libpng_jll.PATH. This may fail, cause incorrect answers, or produce other errors.
WARNING: redefinition of constant libpng_jll.LIBPATH. This may fail, cause incorrect answers, or produce other errors.
WARNING: redefinition of constant libpng_jll.PATH_list. This may fail, cause incorrect answers, or produce other errors.
WARNING: redefinition of constant libpng_jll.LIBPATH_list. This may fail, cause incorrect answers, or produce other errors.
┌ Error: Error watching manifest
│ exception =
│ MethodError: no method matching (::libpng_jll.var"#make_wrapper_dict#10"{libpng_jll.var"#parse_wrapper_platform#9"})(::String, ::Vector{String})
│ The function `make_wrapper_dict` exists, but no method is defined for this combination of argument types.
│ Stacktrace:
│ [1] top-level scope
│ @ ~/.julia/packages/JLLWrappers/GfYNv/src/toplevel_generators.jl:167
│ Revise evaluation error at /Users/user/.julia/packages/JLLWrappers/GfYNv/src/toplevel_generators.jl:167
│
│ Stacktrace:
│ [1] methods_by_execution!(recurse::Any, methodinfo::Revise.CodeTrackingMethodInfo, docexprs::Dict{Module, Vector{Expr}}, mod::Module, ex::Expr; mode::Symbol, disablebp::Bool, always_rethrow::Bool, kwargs::@Kwargs{})
│ @ Revise ~/.julia/packages/Revise/tTIBp/src/lowered.jl:296
└ @ Revise ~/.julia/packages/Revise/tTIBp/src/pkgs.jl:498
|
Another oddity that I suspect is related: when using lazygit, if there have been updates to |
This is like the opposite of an MWE, but I've received a report of a Revise evaluation error while updating packages because a gensym'ed functor didn't have a method it was expecting.
I've not found this posted before here, but I found a very similar stacktrace on the Julia issue tracker: JuliaLang/julia#34598 (comment). There's quite a similarity here — both are trying to find a method for what look to be anonymous/gensym'ed functor created by a JLLWrappers macro.
The text was updated successfully, but these errors were encountered: