Repository navigation
Test installation of every catalog extension on schedule - #935
Draft
ehennestad wants to merge 1 commit into
Draft
ehennestad wants to merge 1 commit into
ehennestad wants to merge 1 commit into
Conversation
ehennestad
added this pull request to stack #934
October 4, 2026 16:59
The update_extension_list workflow gets a second job that installs the latest release of every extension in the catalog, each in its own folder with the core schema. The job summary lists, per extension, the catalog version, the latest release and the number of releases on PyPI, and the installation result. The job fails when an extension does not install. It runs separately from the list update, so a failing extension does not block the update. tools/maintenance/matnwb_testExtensionInstallation runs the same check locally. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ehennestad
force-pushed
the
test-extension-installation
branch
from
October 6, 2026 18:10
ff0cc30 to
b9bd3ce
Compare
This branch has not been deployed
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
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.
Motivation
Problem — When an extension in the catalog stops installing in MatNWB, the maintainers find out only when a user reports it. Before #931, #932 and #933, three of the 30 catalog extensions (
ndx-odor-metadata,ndx-microscopyandndx-franklab-novela) failed to install, for three unrelated reasons, and nothing in CI showed it. The scheduledupdate_extension_listworkflow keeps the list of extension names up to date, but never installs one, and the test suite installs onlyndx-miniscopeandndx-photostim.Solution — The workflow now also installs the latest release of every catalog extension on its schedule. The job summary lists each extension's versions and installation result, and the job fails when an extension does not install.
What changed
update_extension_list.yml,test_extension_installation, runs on the same schedule and on manual dispatch.Installedor the error message.tools/maintenance/matnwb_testExtensionInstallationruns the same check locally.Examples
The report
Running the check on this branch, which does not include the fix in #931, gives this summary (abridged) and fails because of
ndx-odor-metadata:addpath(genpath("tools")) matnwb_testExtensionInstallation()How to test
Run the snippet above from the MatNWB root folder. To run the job on GitHub, dispatch the workflow from this branch; note that the dispatch also runs the existing
update_extension_listjob, which pushes an updatednwbInstallExtension.mtomainwhen the catalog has changed.Checklist
fix #XXwhereXXis the issue number?🤖 Generated with Claude Code