Skip to content

Issue with Project Indexing in codebase-memory-mcp v0.10.2 #1570

Open

Description

@kenvqin

Version

codebase-memory-mcp 0.10.2

Platform

Windows (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

ui

What happened, and what did you expect?

Image

I am writing to report an indexing issue that we have encountered with one of our projects.

In version 0.81, the indexing for this particular project worked without any problems. However, after upgrading to codebase-memory-mcp version 0.10.2, the error shown in the attached screenshot occurs specifically for the project depicted. I would also note that two other smaller projects are indexed correctly in the same environment.

We have already attempted to delete the project index and perform a fresh re‑indexing, but the issue persists and does not resolve.

We would greatly appreciate your assistance in investigating this matter. Please let us know if you require any further details or log files.

Reproduction

❯ codebase-memory-mcp cli index_repository '{"repo_path": "E:\Guigug.His-NET4.8"}'
Preparing one-shot local CBM command...
level=warn msg=mem.allocator.preloading_completed still_preloading=false detail=allocator_was_still_preloading,_so_arena_creation_and_purging_were_disabled;_process_init_completed_explicitly
level=info msg=mem.allocator.owned classes=all
level=info msg=mem.init budget_mb=11411 total_ram_mb=32605 source=ram_fraction
warning: passing raw JSON to 'cli index_repository' is deprecated and will be removed in a future release; use flags (run 'cli index_repository --help'), --args-file , or piped stdin.
Running index_repository locally...
{"project":"E-Guigug.His-NET4.8","excluded":{"dirs":[".codebase-memory",".git",".vs","packages","Publish/Server/bin"],"count":292,"truncated":true},"skipped_count":0,"parse_partial_count":0,"not_indexed_files_count":3282,"not_indexed_files":{"files":[{"path":"Guigug.His.v12.suo","reason":"gitignore"},{"path":"UpgradeLog.htm","reason":"gitignore"},{"path":"UpgradeLog2.htm","reason":"gitignore"},{"path":"Publish/Server/Install/dotNetFramework.exe","reason":"ignored-suffix"},{"path":"Publish/Server/Install/KB2468871.exe","reason":"ignored-suffix"}],"count":3282,"truncated":true,"note":"Excluded by design (gitignore/.cbmignore/skip-lists); examples only 鈥?full list in 'logfile'."},"nodes":256844,"edges":555588,"adr_present":false,"adr_hint":"Project indexed. Consider creating an Architecture Decision Record: explore the codebase with get_architecture(aspects=['all']), then use manage_adr(mode='update') to persist architectural insights across sessions.","artifact_present":true,"status":"indexed"}
Completed index_repository (9840 ms)

Logs


Diagnostics trajectory (memory / performance / leak issues)


Project scale (if relevant)

45546 files

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
    priority/highNeeds near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.
    on Aug 12, 2026
  2. DeusData commented on Aug 12, 2026

    @DeusData
    Owner

    Thank you @kenvqin. The screenshot and command output show two different outcomes: indexing completed successfully with 256,844 nodes, while the graph page failed with the server response JSON parse failed.

    The current layout path explains that failure: cbm_layout_to_json() serializes with YYJSON_WRITE_ALLOW_INVALID_UNICODE, then handle_layout() immediately reparses the generated text with strict yyjson_read(..., 0). One invalid source string can therefore serialize and then make the whole UI layout reparse fail. This is a UI serialization bug, not an indexing failure, and is routed priority/high under #396. Thank you for including both the screenshot and successful CLI result.

  3. DeusData commented on Oct 19, 2026

    @DeusData
    Owner

    Thank you again for including the successful CLI result alongside the UI failure. The earlier response separated graph-page serialization from indexing, and I have no new fix result to add. No repeat indexing run is requested as part of this follow-up.

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 workingpriority/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

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions