Skip to content

fix: dedupe conflict findings by document pair - #15

Closed
slegarraga wants to merge 2 commits into
AgentPostmortem:mainfrom
slegarraga:main
Closed

fix: dedupe conflict findings by document pair#15
slegarraga wants to merge 2 commits into
AgentPostmortem:mainfrom
slegarraga:main

Conversation

@slegarraga

Copy link
Copy Markdown

Closes #3.

Deduplicates conflict findings by unordered document pair so multiple chunks from the same documents produce one conflict, not one per chunk pair. Applies the dedupe to both the official-official and official-informal loops.

Adds regression tests for both duplicate-chunk shapes.

Verified with pytest tests/test_conflicts.py -k conflict (12 passed; the remaining async DB tests require a local Postgres and were not runnable here).

@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown

Welcome, @slegarraga, and thanks for your first pull request to VaultRAG.

A quick look at CONTRIBUTING.md covers how things are set up and run here.

I'll review this shortly. Ask anything in the thread if something is unclear.

@royalpinto007

Copy link
Copy Markdown
Collaborator

Closing this PR.

The author is no longer an active contributor on these repositories, so this cannot be carried through review or iterated on.

The underlying issue stays open and is available for anyone who wants it. If you were looking at this change, please do open a fresh PR, it is very welcome.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

detect_conflicts reports the same document pair once per chunk pair, so one disagreement prints four times

2 participants