Closed jtpio closed 2 weeks ago
This is likely related to a new release of an upstream dependency, although not sure which one yet.
That would likely be https://github.com/jupyterlab/jupyterlab_server/releases/tag/v2.27.0
Can you confirm this by pinning?
Gonna try that in a draft PR.
That would likely be https://github.com/jupyterlab/jupyterlab_server/releases/tag/v2.27.0
Yes, pinning jupyterlab_server
makes the CI checks pass on https://github.com/jupyterlab/jupyterlab/pull/16223 :
@divyansshhh what do you think?
According to the changelog this is the only PR released in 2.27.0
: https://github.com/jupyterlab/jupyterlab_server/pull/448
cc @divyansshhh as the author of the PR, who may also have an idea of what may be causing the issue.
Taking a look
The issue was due to moving the ENV_CONFIG_PATH import to the top of the file.
I'm raising another PR in jupyterlab_server to fix this.
Raised jupyterlab/jupyterlab_server#450
Closing as fixed by https://github.com/jupyterlab/jupyterlab_server/pull/450, released in https://github.com/jupyterlab/jupyterlab_server/releases/tag/v2.27.1.
Thanks @divyansshhh and @krassowski!
Looks like the Python tests started to fail on CI.
This was originally noticed after rebasing https://github.com/jupyterlab/jupyterlab/pull/16005.
But reproducible on the latest commit on the
main
branch: 8819549495cd11470b4db7464d1d59c53cfce787Example run: https://github.com/jupyterlab/jupyterlab/actions/runs/8773764108/job/24110994049