test: preview jupyterlab image built against nb-nebi-kernels kernel-followups branch#183
Draft
viniciusdc wants to merge 4 commits into
Draft
test: preview jupyterlab image built against nb-nebi-kernels kernel-followups branch#183viniciusdc wants to merge 4 commits into
viniciusdc wants to merge 4 commits into
Conversation
Point the nb_nebi_kernels pypi dependency at the kernelFollowUps branch so CI produces a preview singleuser image for integration-testing the non-ready-kernel and discovery-refresh changes, instead of the released 0.1 wheel. Relock accordingly. Test-only, not for merge.
…ntend Point jupyterlab-launchpad at git main (which now carries the nb-nebi-kernels state-metadata consumption + explicit refresh trigger) instead of the 1.0.5 PyPI release that predates it, so the preview image renders the Nebi kernel states. Relock accordingly.
…end loads launchpad main (post-#80) is built against JupyterLab 4.3.4+/4.4.x; the image pinned 4.2.5, so its federated modules could not resolve (docregistry/outputarea/ nbformat unsatisfied) and the kernel-state UI would not render. Bump the image so build and runtime align. Resolves to 4.5.10.
…ll_status gate/backfill, tomli, guard)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this is
A test-only, do-not-merge PR to produce a preview JupyterLab singleuser image whose
nb_nebi_kernelscomes from the open follow-ups branch instead of the==0.1PyPI wheel, so we can exercise the non-ready-kernel / discovery-refresh changes in a live cluster.images/jupyterlab/pixi.toml:nb_nebi_kernelsnow installs fromgit+https://github.com/MUFFANUJ/nb-nebi-kernels@kernelFollowUps(the PR under test: Handle non-ready Nebi kernels and avoid unnecessary discovery refreshes nb-nebi-kernels#9).images/jupyterlab/pixi.lock: relocked; resolves to0.1.dev31+gdae3322(the PR head).How to use the build
CI on this PR pushes
quay.io/nebari/nebari-data-science-pack-jupyterlab:pr-<N>and:sha-<short>. Pin thesha-tag in the deployment'sdata-science-packvalues (bothjupyterhub.custom.profiles[*]image choices andjupyterhub.singleuser.image.tag) to run it.Scope
Validates the kernel-state fixes (remote-not-pulled stub routing, discovery-refresh short-circuit). It does not cover the
install_statuspath, which depends on the still-unmerged nebi explicit-install work. Revert / close once validated — this must not merge tomain.