Repository navigation
[Bug Fix] component() rejects assumed_system_requirements in reqs - #523
Merged
hoe-jo merged 1 commit intoOct 15, 2026
Conversation
component_impl already collects AssumedSystemRequirementsInfo (ASR) into the upstream lobster level, and both sibling rules (component_update,dependable_element) already accept the provider- only component_test's attribute schema was missing it. This blocked SEooCs from tracing component requirements directly to ASRs without a feature-requirements layer, failing with lobster error: unknown tracing target req <pkg>.<AssumedSystemReq>.
Ehrja
marked this pull request as ready for review
October 15, 2026 06:25
Ehrja
requested review from
LittleHuba,
castler,
hoe-jo,
limdor and
ramceb
as code owners
October 15, 2026 06:25
hoe-jo
approved these changes
Oct 15, 2026
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.
component_impl already collects AssumedSystemRequirementsInfo (ASR) into the upstream lobster level, and both sibling rules (component_update, dependable_element) already accept the provider - only component_test's attribute schema was missing it.
This blocked SEooCs from tracing component requirements directly to ASRs without a feature-requirements layer,
failing with lobster error:
unknown tracing target req <pkg>.<AssumedSystemReq>.