fix: Mitigate extension host crash from Qdrant batch deletes #5521
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes issue #5516, where the extension host would crash due to repeated "Bad Request" errors from the Qdrant
deletePointsByMultipleFilePathsfunction.The root cause was large batches of file deletion requests overwhelming the Qdrant API, with no retry logic or graceful error handling to prevent a crash loop.
Key changes in this PR include:
deletePointsByMultipleFilePathsfunction inqdrant-client.tsnow splits large deletion requests into smaller, more manageable chunks.scanner.tsandfile-watcher.tsservices now log errors from failed chunks and continue processing, preventing the extension from crashing. A consolidated error is thrown at the end if any chunks failed permanently.qdrant-client.spec.tsto validate the new chunking, retry, and error-handling logic.Closes #5516