Skip to content

Indexing failed: Invalid string length #25

Closed

Description

@NextDesign1

When indexing a large monorepo, once the embeddings are generated, it can result in the following error message.

Embedding complete: 200000 texts in 2500.0s
Store phase: storing 22000 file(s) into vector database...
Store phase complete: 0 files stored in 0.1s (0 total chunks)

Indexing failed: Invalid string length

This unfortunately seems to throw away all of the computed embeddings.

Activity

  1. MrDoe commented on Aug 4, 2026

    @MrDoe
    Owner

    Thanks for reporting this issue! I'll take a look into it.

  2. linked a pull request that will close this issueperf: accelerate the index store phase #27on Aug 6, 2026
  3. MrDoe commented on Aug 6, 2026

    @MrDoe
    Owner

    The latest pr should also have solved this issue. Can you please try it again with the newest version?

  4. self-assigned this
    on Aug 6, 2026
  5. added
    bugSomething isn't working
    on Aug 6, 2026
  6. NextDesign1 commented on Aug 8, 2026

    @NextDesign1
    Author

    Unfortunately I'm still seeing this.

    Store phase: 6 files stored in 0.2s (running total 120000 chunks)
    Index pass complete: 120000 total chunks (20000 files processed)
    
    Indexing failed: Invalid string length
    
  7. MrDoe commented on Aug 8, 2026

    @MrDoe
    Owner

    Can you please post me the output of your opencode-rag status here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions