mudler / mudler/LocalRecall

DELETE /api/collections/name/sources residuals

Open
#32 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
974
Forks
121
Avg merge
5h 52m
Merged PRs (30d)
1

Description

After removing a source from my collection using the DELETE method, a text file in the LocalRecall container containing the raw text of the source persists and continues to be vectorized periodically.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue through DELETE /api/collections/name/sources and inspect the LocalRecall container for the source's raw text file and continued vectorization. Trace the deletion entry point and the periodic vectorization path. Done means the source text is removed and is no longer vectorized after deletion.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.