JE Server Disconnecting Beta Issue

[ivonnem3]

Beta User testers reported that the backend server would disconnect after a while and not allow users to generate links. Ivonne will check in with the team about the issue, but needs to be tested when the app is deployed.

[adamblake]

@agriyakhetarpal I'm not sure this is a back-end issue as the server can't really "disconnect" since it's just an API server running. Do you know if this is a case of the token not being refreshed or something like that?

[agriyakhetarpal]

Hi @adamblake, I haven't encountered this issue in my own testing of the application – the frontend has not lost connection with the backend so far, so I think @ivonnem3 might have more information about this. We refresh the token at a few points, but if we should do so more frequently, that should be trivial to configure.

[youngsaver-skewthescript]

Target date pushed from 10/1 -> 10/3 due to illness

[ivonnem3]

This was an issue I brought up on August 8th via our Slack channel. The initial Slack thread discussed how users would not be able to create a link unit the kernel loaded. Later in the same Slack thread, I mentioned that after some time, I was not able to generate a link, although the kernel was loaded. I shared the following image on the Slack channel, and I think this is what the users were experiencing.

[agriyakhetarpal]

Thanks for the extra context, @ivonnem3!

The initial Slack thread discussed how users would not be able to create a link unit the kernel loaded.

I had opened a PR for this here back then: JupyterEverywhere/jupyterlite-extension#192, but we decided that this works around a backend bug, that should ideally be handled by the backend, as per @krassowski's report about it in #9, which apparently has been resolved, but only partially (as discussed later in the thread around 9–11 August).

Later in the same Slack thread, I mentioned that after some time, I was not able to generate a link, although the kernel was loaded.

Unfortunately, I tried to reproduce the behaviour you mentioned above on https://dev.jupytereverywhere.org/ just now, by trying to share a notebook before the kernel loads, but at the moment I'm facing some trouble sharing the notebooks altogether. I've sent a message on Slack internally highlighting this issue.