Closed tusharkhot closed 3 weeks ago
Looks like this just got fixed! Thanks! FWIW this has been a transient issue last week and completely stopped working on Friday. Hopefully this was a fix and not just luck.
PS: I also replaced run_jupyter.remote
with run_jupyter.spawn
and that wasn't working either.
Let us know if it recurs!
Looks like this issue is back. See the app:
ap-7ttuFE3RVDSnprmVJZQkQD fc-01J0Y93AW71N46DZVG17E68503 Input ID: in-01J0Y93AWEK55RRAH7KCX8QQV9
I am not able to reproduce it with my simple script, but you can see the errors in the app
@mwaskom Should I open a new issue?
Hey, googling the error message tells me that this is a fairly common issue with Jupyter notebooks: https://stackoverflow.com/questions/55014094/jupyter-notebook-not-saving-xsrf-argument-missing-from-post
Just did a cursory search and not sure if there's an obvious root cause or way to avoid. But it does make me suspect there may not be a modal-specific issue here?
So looks like its an issue with the Modal queue. The hostname gets pushed to jupyter-url-queue-0
but my code keeps waiting for the hostname. I thought its because of the _xsrf error message but its this specific queue. Once I change the queue name to jupyter-url-queue-1
, things work fine.
I am running Jupyter on T4 GPUs and getting XSRF issues that blocks the queue. I have slightly modified the jupyter notebook example for reproduction.
If you run
modal run
, you will see the xsrf issue and the code will never reach the "Found host:" line even though the url is added to the queue.Stack trace: