Improve Optional Dependency Error Handling & Regression Tests #9
Conversation
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
…ng torch, vision encoder
… to ensure PerceptionEncoder raises descriptive ImportErrors when the vision stack is absent.
…g components for the perception encoder are explicitly listed in the guidance message.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
This PR enhances regression tests to ensure that missing optional dependencies, particularly vision-stack components and torch, produce clear, actionable error messages across PerceptionEncoder and VFSStore.
Changes
Why
Improves developer experience by making dependency-related failures easier to diagnose and ensuring consistent behavior in environments with optional or lightweight installations.
Checklist