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
I've never ran into this before, but I'm having trouble loading the extension in SnoopCompile:
julia> using SnoopCompileCore julia> tinf = @snoop_inference begin import Thermodynamics as TD end SnoopCompileCore.InferenceTimingNode(SnoopCompileCore.InferenceTiming(InferenceFrameInfo for Core.Compiler.Timings.ROOT(), 0.335086625, 0.335086625), 747264.775509541, SnoopCompileCore.InferenceTimingNode[], nothing, #undef) julia> using PyPlot julia> import PyPlot julia> using Profile julia> using SnoopCompile julia> using SnoopCompile: pgdsgui julia> mref, ax = pgdsgui(tinf); ERROR: MethodError: no method matching pgdsgui(::SnoopCompileCore.InferenceTimingNode) Stacktrace: [1] top-level scope @ REPL[8]:1
If I grab the extension directly, it seems like it has loaded:
julia> SCPyPlotExt = Base.get_extension(SnoopCompile, :SCPyPlotExt); julia> SCPyPlotExt.pgdsgui pgdsgui (generic function with 3 methods)
But then I still run into a strange (seemingly loading) issue when trying to use it:
Any idea what I'm doing wrong here?
The text was updated successfully, but these errors were encountered:
Ah, I think pgdsgui is just not getting imported in the extension. I can open a PR.
pgdsgui
Sorry, something went wrong.
@Sbozzolo beat me to it! Will be closed by #398.
Closed by #398
No branches or pull requests
I've never ran into this before, but I'm having trouble loading the extension in SnoopCompile:
If I grab the extension directly, it seems like it has loaded:
But then I still run into a strange (seemingly loading) issue when trying to use it:
Any idea what I'm doing wrong here?
The text was updated successfully, but these errors were encountered: