fonsp / Pluto.jl

🎈 Simple reactive notebooks for Julia
https://plutojl.org/
MIT License
4.94k stars 285 forks source link

Firefox can't connect to Pluto after a day #1025

Closed ThatcherC closed 3 years ago

ThatcherC commented 3 years ago

I'm having an issue with Pluto in Firefox on Linux, which I think might be connected to #848 and #859. I usually start up Pluto with

import Pluto
Pluto.run(require_secret_for_access=false, require_secret_for_open_links=false)

This runs well for awhile (at least one day, sometimes a few days) and then at some point I'm seemingly unable to connect to the Pluto server to make a new notebook. Interestingly, though, notebooks that were running already still work fine, except that I see a repeated error in the web console:

Screenshot from 2021-03-25 14-04-59

I am running:

I don't see any errors in the Julia shell where I'm running Pluto (except errors from my own code). Here's what I see in the Firefox web console when I start a new notebook from the Pluto instance that had been running fine for a day or two:

Screenshot from 2021-03-25 13-42-44

It's an odd bug to me - Pluto starts up perfectly and works very well for at least a day every time, but then eventually I get back to this state.

Let me know if there are other tests I can run or logs I can share! Thanks!

fonsp commented 3 years ago

Thanks! Some follow-up questions:

ThatcherC commented 3 years ago
ThatcherC commented 3 years ago

Okay, took a while to get the error again but I got it. I'm on Julia 1.6 now, and using Pluto#main. I tried to open a new notebook inf Firefox this afternoon (from a Pluto session that's been running for a few days) and the front page wouldn't load (see the first picture below). I got the same thing in a Firefox Private Window, and saw an error being output on the browser console very rapidly (see second picture below):

Screenshot from 2021-03-29 18-08-01

Screenshot from 2021-03-29 18-06-06

Opening the front page in Chrome was successful! I was open to open up my notebook with no problems. I did see the same error in the browser console, but only once:

Screenshot from 2021-03-29 18-10-56

I hope this is helpful! Let me know if there are other tests I should run as well.

fonsp commented 3 years ago

very rapidly

What do you mean exactly? Twice per second? Definitely more than twice per second?

Follow-up questions:

FYI the 404 error was "intentional", but I have removed the warning message in a recent commit. It should not be related.

ThatcherC commented 3 years ago

"Very rapidly" was at least twice person, probably more like 10 or 20 times per second. I wasn't able to time it.

For the follow up questions:

pankgeorg commented 3 years ago

Closing due to lack of progress - let's continue in #848 if we have new data