Skip to content

C# overloaded methods not indexed #1407

Open

Description

@tool-buddy

Version

codebase-memory-mcp 0.9.1-rc.1

Platform

Windows (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

ui

What happened, and what did you expect?

What happened?
Regarding C# code, the indexer does not index overloaded constructors/methods. Only the last defined overload is retained in the knowledge graph.

What did you expect?
That all the c# methods should be indexed.

Reproduction

1. The code
Unity-Technologies/UnityCsReference / 4f66825 / Editor/Mono/Overlays/OverlayAttribute.cs
https://github.com/Unity-Technologies/UnityCsReference/blob/2022.3/Editor/Mono/Overlays/OverlayAttribute.cs

2. The exact command
codebase-memory-mcp cli search_graph --label "Method" --name_pattern "^OverlayAttribute$" --project "unity-api-2022.3"

3. What the output was vs. what it should have been.
total: 1 results: 1 (rows: name label lines in out; qn = group prefix + "." + name) unity-api-2022.3.Editor.Mono.Overlays.OverlayAttribute.OverlayAttribute (Editor/Mono/Overlays/OverlayAttribute.cs): OverlayAttribute Method 195-198 2 1 has_more: false
It should have been 4 results

Logs


Diagnostics trajectory (memory / performance / leak issues)


Project scale (if relevant)

300.000 node / 800.000 edge / 8.000 file

Confirmations

  • I searched existing issues and this is not a duplicate.
  • My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.

Activity

  1. added
    parsing/qualityGraph extraction bugs, false positives, missing edges
    ux/behaviorDisplay bugs, docs, adoption UX
    windowsWindows-specific issues
    on Aug 1, 2026
  2. adfjadfj16-a11y commented on Aug 1, 2026

    @adfjadfj16-a11y
  3. tool-buddy commented on Aug 1, 2026

    @tool-buddy
    Author

    Hi,
    I don't know about other programming languages.
    The issue was there even in version 0.9.0.
    I will let you know if I have useful logs in the future.
    Thank you

  4. added
    priority/highNeeds near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.
    on Aug 3, 2026
  5. added this to the 0.9.1-rc milestone on Aug 3, 2026
  6. DeusData commented on Aug 3, 2026

    @DeusData
    Owner

    Thank you for the overload-specific reproduction. Current storage identity is unique on (project, qualified_name), while the C# method lookup resolves by type and bare method name without arity or signature. That combination can collapse overloads exactly as reported, so this is routed at high priority in 0.9.1-rc. Also, the earlier support-style comment was not posted by the maintainer account or project team; please disregard it. Your report is open and tracked here.

  7. DeusData commented on Sep 3, 2026

    @DeusData
    Owner

    Maintainer notice: please disregard comments from @adfjadfj16-a11y on this thread

    @adfjadfj16-a11y is not a maintainer of this project and does not speak for it. That account has posted replies on 17 threads here written in the project's voice — promising merges, announcing that a case has been "escalated to the development team", asking to close issues, and in some threads replying as though it were the author of someone else's pull request. None of those were maintainer decisions, and none of them carried any weight.

    @DeusData is the only account that gives a maintainer response on this repository. If a comment about the fate of your issue or pull request did not come from @DeusData, it is not a decision, however official it reads.

    If you were waiting on something because of one of those comments — a promised merge, a review "immediately", a request to close your ticket — I am sorry. That was noise you had no way to identify as noise, and it should not have been on your thread. Your issue or PR is judged on its own merits, and I will answer it here myself.

    Nothing in this notice reflects on your contribution. Thank you for your patience, and thank you for the work.

  8. DeusData commented on Oct 19, 2026

    @DeusData
    Owner

    Thank you again for the Unity overload example and version confirmation. I have no new fix to report for the collapsed constructor/method identities. No broader language survey or extra logs are requested from you; the existing four-versus-one result is the relevant case.

  9. DeusData commented on Oct 25, 2026

    @DeusData
    Owner

    Thank you for the Unity overload example. The four-versus-one result is sufficient for maintainer investigation of constructor/method identity; no broader survey or logs are needed. Sorry for the delay; this is waiting on maintainer follow-up, and I’ll follow up soon.

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/highNeeds near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.ux/behaviorDisplay bugs, docs, adoption UXwindowsWindows-specific issues

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions