Skip to content

graph: same clobber class as #787 in env-access CONFIGURES sources and resolve_file_throws #842

Closed

Description

@DeusData

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.

Refs #787, #828.

Activity

  1. added
    bugSomething isn't working
    parsing/qualityGraph extraction bugs, false positives, missing edges
    priority/normalStandard review queue; useful PR with ordinary maintainer urgency.
    on Jul 4, 2026
  2. DeusData commented on Jul 8, 2026

    @DeusData
    OwnerAuthor

    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.

  3. added this to the 0.9.1-rc milestone on Jul 8, 2026
  4. added a commit that references this issue on Jul 9, 2026
    6b2cd08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingparsing/qualityGraph extraction bugs, false positives, missing edgespriority/normalStandard review queue; useful PR with ordinary maintainer urgency.

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions