DrChainsaw (Oct 16 2021 at 11:15): DrChainsaw (Oct 16 2021 at 11:15):This is probably not easy to debug from afar, but could anyone think of reasons why Revise would not work when running as an interactive job on a compute cluster (lsf in this case)?
The job spins up and starts a julia session with the current project active. Doing using Project works just fine and all data and .julia stuff is perfectly accessible. Packages from startup.jl (e.g. OhMyRepl) seem to be correctly loaded Revise is loaded and doing things like Revise.revise(MyProject) returns true without warning.
Things work as expected if I run in a terminal on the job submitting host (even if I ssh into it form another computer e.g. using VS code remote).
DrChainsaw (Oct 28 2021 at 11:34):Turns out this section in the docs was the answer: https://timholy.github.io/Revise.jl/stable/config/#Polling-and-NFS-mounted-code-directories:-JULIA_REVISE_POLL-1
It is a bit unreliable as the network seems slow and sometimes it takes up towards 30 seconds before Revise notices that the file is changed and in the meantime the old definition is used. Most likely can't blame this on Revise though.
Notification Bot (Oct 28 2021 at 11:34):DrChainsaw has marked this topic as resolved.
Last updated: Nov 06 2024 at 04:40 UTC