No i18n support.
https://github.com/jupyter/notebook/issues/870
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | rook | T121478 i18n support | |||
Resolved | rook | T338981 [Rollback] paws to jupyterlab 4.0 | |||
Resolved | aborrero | T338778 cloudservices2004-dev: reimage into new network setup | |||
Invalid | None | T339869 codfw1dev: LDAP database content seems to have lost years of content | |||
Resolved | Andrew | T339961 Cannot deploy magnum to paws-dev in codfw1dev | |||
Resolved | Andrew | T341355 Magnum control plane trying to access https://discovery.etcd.io/new?size=1 | |||
Resolved | None | T340684 Cannot create volumes in codfw1dev paws-dev | |||
Resolved | None | T320934 sparql failing to build |
Event Timeline
Comment Actions
Looks like this was unblocked upstream last month in notebook 7. We should be able to deploy though we would remove sparql as noted in T320934. That the jupyterlab plugin for sparql appears to be abandoned and notebook does not, this seems reasonable to me.
Comment Actions
Though it looks like we will also have to move jupyterlab to 4.0.2. Thus T338981 is also in conflict with this ticket.
Comment Actions
Looks like notebook 7 has a bug that causes direction to /tree rather than /lab
https://github.com/jupyter/notebook/issues/6954
Though it is being worked on
https://github.com/jupyter/notebook/pull/6997
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2023-08-30T12:39:25Z] <Rook> Upgrade notebook allowing i18n support T121478