Update from 19.12 to 19.14 - often hangs when opening notebook

[BioTurboNick]

Seems to be stuck while loading packages.

Killing the notebook process and restarting it can resolve it.

Problem is that I have trouble reproducing it. It's happened twice now today. If I can learn more, I'll add to this.

Working: 0.19.12
Not working: 0.19.14

(edited to remove irrelevant parts of image)

[fonsp]

Looking at the diff, relevant changes could be:

• PlutoPkg: if Pkg.resolve fails, try updating the registries #2298 (this change happens before instantiating the environment, which already happened in the screenshot)
• Using RegistryInstances.jl to avoid some Pkg internal API #2118 #2289 (but you would probably get an error message in the terminal if this fails)
• Refactor WorkspaceManager #2318
• 9aad08d (but this just adds more safety)

[fonsp]

It could actually be #2318 , in the screenshot, it looks like Pluto's package manager finished (you can see the ✅), but the first cell that should run (the cell with imports) is not yet running (the timer is still at ---). Perhaps the notebook is stuck creating a workspace process...

EDIT: after a second look at the PR I am fairly sure that it is not the cause.

[rikhuijzer]

Could it be that updating the registry fails for some reason? I am currently also having some problems with a registry update inside a Docker (Pluto 0.19.16). I one time saw an error from HTTP that the transfer speed to https://pkg.julialang.org was below 1kB/s.

@BioTurboNick, you're not on Windows, right?

[BioTurboNick]

In this case it was running on an AWS Linux computer.

[fonsp]

If it is the case that it gets stuck on the registry update, we will be able to see that after #2399 :)

[fonsp]

#2399 has been released

After loading Pluto, open a notebook, and then press F12 to open the web developer tools. Go to the JavaScript console, and type:

PLUTO_TOGGLE_PROCESS_TAB()

to enable the feature.

Could you enable the feature, and let us know the next time a hang happens?

[BioTurboNick]

I think I'll close this for now - I haven't noticed it in a while. I'll revisit if I observe it again.