You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
probe_reference_closure is blind on R13/R14 — no locatable handle stream boundary #84
probe_reference_closure's hard-reference measurement is blind on R13/R14: those records expose no locatable handle stream (292 records per file report "no boundary"), so the closure argument that settles "declared but unwalked = over-declaration" on R2004+ cannot be run on that band. Deriving the R13/R14 handle-area boundary (the spec's common-entity-data layout puts handles after the object data, but nothing self-delimits) would extend the closure proof to all seven versions.
The Corpus job #225 adds now reports this in CI instead of counting the files as closed: "Reference closure: … NOT MEASURED on 8 whose records expose no handle-stream boundary" (the 7 nextgis R14 drawings and ACadSharp's sample_AC1014.dwg, 1,242 records), Measure run 40297255178. tools/corpus/baseline.tsv pins refs 0 and no_boundary per file, so the day this is fixed the baseline moves with it.
Activity
DrunkOnJava commentedon Oct 26, 2026
The Corpus job #225 adds now reports this in CI instead of counting the files as closed: "Reference closure: … NOT MEASURED on 8 whose records expose no handle-stream boundary" (the 7 nextgis R14 drawings and ACadSharp's
sample_AC1014.dwg, 1,242 records), Measure run 40297255178.tools/corpus/baseline.tsvpinsrefs0 andno_boundaryper file, so the day this is fixed the baseline moves with it.