Prevalidate plugin entrypoints to check for broken plugins#446
Merged
Conversation
Signed-off-by: Yondon Fu <[email protected]>
Contributor
Author
|
The broken plugin used for testing is at yondonfu/kaleido-scope@0eb2585 |
Contributor
Author
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.

Summary
_prevalidate_entrypoints()which enforces a single entry point per plugin, records failures asFailedPluginInfo, and blocks broken entry points from being registered in pluggyGET /api/v1/pluginsnow returnsfailed_pluginsalongsidepluginsso the frontend can surface errorsPluginsTabshows a warning banner and per-plugin error details when plugins fail to loadTest plan
uv run pytest tests/test_plugin_manager.py— all 8 new tests pass🤖 Generated with Claude Code