-
Notifications
You must be signed in to change notification settings - Fork 22
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
Infiltrating package functions. #80
Comments
Impossible to say what's going on without a MWE. This does look like a false positive though. Technically, I'm only checking whether Aside: I'd recommend not loading |
It works with Aside: When I use just if isdefined(Main, :Infiltrator)
Main.infiltrate(@__MODULE__, Base.@locals, @__FILE__, @__LINE__)
end |
Right, that's why I suggested only adding |
Re MWE: If you can share VAEs.jl then I can work with that :) |
VAEs.jl is total mess... rather try this. Run the |
works fine for me. What Julia version/OS are you on? |
Oh... come on! :-D julia> versioninfo()
Julia Version 1.7.3
Commit 742b9abb4d (2022-05-06 12:58 UTC)
Platform Info:
OS: Linux (x86_64-pc-linux-gnu)
CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-12.0.1 (ORCJIT, skylake)
Environment:
JULIA_PKG_USE_CLI_GIT = true
JULIA_NUM_THREADS = 8
|
Do you have anything in your startup.jl (like e.g. OhMyREPL)? |
No, it is empty. |
Just to confirm. Did you use inline evaluation (Ctrl+Enter) for that or copy-paste it into the REPL? |
Inline, is it a problem? Oh I see... copy-paste works. |
Yes, as per the readme:
I'll add some more info to the error message :) |
My bad. Sorry and thank you! 👍 |
Hello,
I am trying to debug one of the function from my
VAEs
package. I have Infiltrator.jl and Revise.jl added to my main environment@v1.7
. For debugging purposes I am running this code inVAEs
environment (default active environment in VS Code). What does the message "Cannot infiltrate while the REPL is idle. This typically..." means?Here is the status of my
@v1.7
environment.And here is the debug function.
Basically I do not know the right workflow for package development (debugging). I can use debugger built in the VS Code but in my case I need the only sizes of my tensors and debugger gives me too much irrelevant and confusing informations.
The text was updated successfully, but these errors were encountered: