You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add ability to customize or disable activity reporting to the JupyterHub handler. Currently, all requests to the proxy get marked as activity. This means if you leave your browser open with an open tab that goes through the proxy and don't interact with the page your JupyterHub pod will not get culled!
Who would use this feature?
Anyone who wants to leverage JupyterHub pod culling that has a better was of detecting activity.
The text was updated successfully, but these errors were encountered:
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
Welcome to the Jupyter community! 🎉
sdmichelini
added a commit
to sdmichelini/jupyter-server-proxy
that referenced
this issue
Apr 15, 2024
Allows proxy to be configured if it reports back
to JupyterHub. In some cases the proxy will always detect background
activity which means that the pod will never get culled. In
this case you must disable recording and use an alternative
source of activity(outside of this MR)
Closesjupyterhub#471
Proposed change
Add ability to customize or disable activity reporting to the JupyterHub handler. Currently, all requests to the proxy get marked as activity. This means if you leave your browser open with an open tab that goes through the proxy and don't interact with the page your JupyterHub pod will not get culled!
Who would use this feature?
Anyone who wants to leverage JupyterHub pod culling that has a better was of detecting activity.
The text was updated successfully, but these errors were encountered: