403 executing a mutation

[kinow]

Describe the bug

A strange bug. I noticed this morning that after leaving the workflow running for a very long time in the browser, it gave me an error executing a mutation.

So went for lunch and left a workflow running. Came back and waited a bit more. It (five) was probably left unattended for 1-2 hours. I left the browser window in another Linux desktop running, with UIS and Flow. No errors in the the log. Then clicked to pause it, but got an error 403?

Release version(s) and/or repository branch(es) affected?

master flow/uis/and UI

Steps to reproduce the bug

Leave JupyterHub + UIS running for a long time, making sure the UIS has been spawned (just open the browser, for instance).

Try clicking on the pause/hold mutation icon.

Expected behavior

The mutation is executed.

Screenshots

See description above.

Additional context

I think it could be due to inactivity in the Hub. There could be a setting somewhere that we can add to keep the connection alive, or send some ping to the backend telling that the session is still active.

I suspect some users of long-running workflows could want to trigger mutations after the UI has been running for a long time, even if they haven't interacted with the browser.

Note that the session is refreshed automatically when you reload the browser, as the cookie is still valid, but I think the token is not.

2021-03-15 14:04:24,656 tornado.access WARNING  403 POST /user/kinow/graphql (127.0.0.1) 25.51ms
2021-03-15 14:04:49,463 tornado.application WARNING  Token stored in cookie may have expired

Pull requests welcome!
This is an Open Source project - please consider contributing a bug fix
yourself (please read CONTRIBUTING.md before starting any work though).

[kinow]

JupyterHub settings that I think could be related:

• refresh_user
• auth_refresh_age
• last_activity_interval
• activity_resolution
• active_user_window

[kinow]

Note: confirm it's still an issue after #711

[MetRonnie]

This has not been seen for a long time; closing.