Repository navigation
Conversation
Require a reached prerequisite with no assignment to fail the full dependency graph. The later logged fallback acts as a canary for evaluators that incorrectly continue the root waterfall. Environment: Datadog workspace Co-Authored-By: Codex GPT-5 <noreply@localhost>
hhan2024
approved these changes
Oct 30, 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.
Motivation
A reached prerequisite flag that produces no assignment is an invalid dependency-graph state. The root evaluation must fail closed instead of treating the missing assignment as a normal condition miss and continuing its allocation waterfall.
Changes
dependent-no-assignment-parentand adependent-no-assignment-rootwhose first allocation depends on the parent'sassignedvariant.GENERALevaluation-event expectations for the parent and root, require no exposures, and reject unmatched telemetry.python3 ci/validate-fixtures.py, the validator unit tests, focused dependent-suite consistency assertions,git diff --check, and both evaluator behaviors.Decisions
The fixture intentionally has no
NOT_ONE_OFallocation because evaluation fails before the dependency operator can logically run. The change is limited to the dependent-flags UFC and case data; it does not alter schemas, validators, evaluator code, system tests, or documentation.Checklist
config/ufc-config.jsonevaluation-cases/