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
graph: same clobber class as #787 in env-access CONFIGURES sources and resolve_file_throws #842
Follow-up disclosed during #828's review (stable USAGE-edge ownership): the same latent bug class — shared directory-module nodes having name/file_path/props clobbered by whichever same-package file processes last, and unguarded merge_update_existing relabeling — also affects the env-access CONFIGURES source attribution and resolve_file_throws. #828 deliberately scoped to USAGE edges; port the same guard + per-file File-node fallback to these two sites, with an #828-style multi-order red fixture.
Thanks for splitting this out from the #828 review. Triage: graph ownership/clobber bug under parsing quality. This is not a general 0.9.0 retest candidate; it needs the same ordered-fixture guard pattern as #828 applied to CONFIGURES source attribution and resolve_file_throws.
Activity
DeusData commentedon Jul 8, 2026
Thanks for splitting this out from the #828 review. Triage: graph ownership/clobber bug under parsing quality. This is not a general 0.9.0 retest candidate; it needs the same ordered-fixture guard pattern as #828 applied to CONFIGURES source attribution and resolve_file_throws.
fix(pipeline): guard env-access CONFIGURES and throws sources against…