Nicolas Brichet
Nicolas Brichet
@bpfrd did you update nbgrader or jupyterlab/notebook recently ? Otherwise, I would suspect an issue with configuration, maybe related to https://github.com/CERIT-SC/nbgrader-k8s (I don't know about that).
For reference https://github.com/CERIT-SC/nbgrader-k8s/issues/11
Thanks for reporting this @JazzDKaur. > 1. The current nbgrader: version 0.7.0.dev The first step is probably to install a stable version of nbgrader: - **not recommanded**: `pip install "nbgrader>0.7,0.8,=0.9"`...
> reading the contents it looks like it should likely work fine to merge and release and follow-up with tests separately. Right, if the `updatableFields` is not available, it will...
Any clue on the check-release failure ? I can't reproduce the steps locally, so it's hard to debug.
Thanks for your feedback @jtpio. > A workaround for now could be to disable the `check-python` step. Until there is a way to skip the `pip install` in the releaser,...
> It looks like we are missing the pre-release specifier: > > ``` > ERROR: Could not find a version that satisfies the requirement jupyter-collaboration-ui>=1.0.0 (from jupyter-collaboration) (from versions: 1.0.0a0,...
Do you know if the `check-python` test has been updated on the releaser ? Otherwise we need to ignore this test to avoid all the following PR to fail, but...
Probably, but I don't know why the test are failing... I'll rebase and we'll see
> Probably, but I don't know why the test are failing... Actually these tests seem to fail with every PR on `2.x` branch.