Skip to content

Fix/dependencymodel fuzz and 2.1.0 release notes#11

Merged
ake2l merged 2 commits into
developmentfrom
fix/dependencymodel-fuzz-and-2.1.0-release-notes
Jun 25, 2026
Merged

Fix/dependencymodel fuzz and 2.1.0 release notes#11
ake2l merged 2 commits into
developmentfrom
fix/dependencymodel-fuzz-and-2.1.0-release-notes

Conversation

@ake2l

@ake2l ake2l commented Jun 25, 2026

Copy link
Copy Markdown
Member

No description provided.

ake2l added 2 commits June 25, 2026 09:41
… fix

The original failure could not be reduced to a shareable schema (~200 tables,
2 stranded nodes), so a single hand-built graph cannot prove the fix holds at
scale. Add a property test that runs 5000 random required+optional cyclic graphs
through dependencyOrderedObjects in both modes -- covering cascade depth,
multiple simultaneous strands and shape diversity a fixture cannot.

Invariant is scoped to the stranding symptom, not "never throws":
- acceptingCycles=true (jdbacl DBUtil's mode): must always resolve completely
  (every node returned, none dropped or duplicated).
- acceptingCycles=false: CyclicDependencyException is legitimate, but the run
  must never strand ("Incomplete nodes left" / a node left out of INITIALIZED).

Verified red against the pre-fix single-pass postProcessNodes (seed 0 strands
t8) and green with the fix.
@ake2l
ake2l merged commit 9aa5de8 into development Jun 25, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant