FTBFS (test failure) with jupyter-client >= 8

Bug #2054342 reported by Andreas Hasenack
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jupyter-notebook (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

________________________ KernelAPITest.test_connections ________________________

self = <notebook.services.kernels.tests.test_kernels_api.KernelAPITest testMethod=test_connections>

    def test_connections(self):
        kid = self.kern_api.start().json()['id']
        model = self.kern_api.get(kid).json()
        self.assertEqual(model['connections'], 0)

> ws = self.kern_api.websocket(kid)
...
> return future_cell[0].result()
E tornado.simple_httpclient.HTTPTimeoutError: Timeout during request

This is failing with jupyter-client 8.6.0-0ubuntu1, which is in noble-proposed, but passes with version 7.4.9-2 from the release pocket.

I found an upstream bug[1], still open, which has a workaround commit[2]: limit jupyter-client to < 8.

Another consumer of jupyter-client investigated a bit further, as they were seeing the same problem, and documented their findings in [3]. That resulted in this commit[4] for that project, but I don't know how to "translate" that to jupyter-notebook.

It might be simpler for noble to just remove jupyter-client 8.6.0-0ubuntu1 from noble-proposed. I don't know why ubuntu went ahead of debian with that upload, there is no closing bug mentioned in d/changelog.

1. https://github.com/jupyter/notebook/issues/6748
2. https://github.com/jupyter/notebook/pull/6749/files
3. https://github.com/jupyter/nbconvert/issues/1964#issuecomment-1495629089
4. https://github.com/jupyter/nbconvert/pull/1972/files

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

This was fixed with https://launchpad.net/ubuntu/+source/jupyter-client/7.4.9-2ubuntu1. jupyter-client 8.6.0-0ubuntu1 was removed from noble-proposed by an AA.

Changed in jupyter-notebook (Ubuntu):
status: New → Fix Committed
Changed in jupyter-notebook (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.