2 Commits

Include renames

Author	SHA1	Message	Date
Daan MeijerandClaude Opus 5.5	6d1f2cc2a1	Par2 merge: a set file matching several releases nearby is ambiguous ... 131 uploads of 1 GiB test files ("kantodoNNN.bin", a.b.test) share their first 16 KiB and size, so all matched one set's single file and became one release of 1,284 files. A par2 file that matches more than one release in the anchor's group and time window is left out; a plain repost of the same file stays apart too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-12 10:15:32 +02:00
Daan MeijerandClaude Opus 5.5	3d0dc6ca1f	The par2 merge: releases whose files one par2 set describes become one ... The prober stores, per probed article that starts a file, the MD5 of its first 16 KiB (file_hashes), and per par2 body the set's whole file list (par2_files, par2_sets): FileDesc holds the same hash per file, whatever the file was renamed to. releases:merge (the merger service, no NNTP) merges every minute the releases of one group, posted within 48 hours of a release holding the set's par2, whose files the set describes, into the one with the most files: chunks, probe candidates, inspections, hashes and counts move; the par2's shared name when none was readable; release_merges keeps what went where. Obfuscated uploads whose files were each a release of their own ("[9/20] - "14f5999a…"", hep: 13,232) become one. Also: corpus_sweep.py counts the marked ranges without psql's command tag. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-12 09:37:35 +02:00