Block a user
Name the database each command uses on stderr (closes #111)
go install @latest must install main's tip; retract v0.0.1; a go-installed binary must say which version it is
v0.0.2 is tagged on main's tip (https://git.eeqj.de/sneak/sfdupes/src/tag/v0.0.2), the same code as v1.0.0-rc2. go install sneak.berlin/go/sfdupes@latest gives it once the Go module proxy…
Add sfdupes info: show the database's details
go install @latest installs the July prototype v0.0.1, and a go-installed binary cannot say which version it is
scan records its own database files when the database is inside a scanned operand
report: never sit silent; show its phases as N of M with progress, elapsed time and ETA
trees: never sit silent; show its phases as N of M with progress, elapsed time and ETA
scan: show each phase as N of M, with progress, elapsed time and ETA, also while it waits
Say which database file each command uses, and document when scan writes to it
Trial run at real scale on the target server before tagging 1.0.0
Diagnosis: the sfdupes in ~/go/bin is almost certainly the old v0.0.1 from July, not the release candidate. That explains all three reports.
Why that build. `go install sneak.berlin/go/s…
resolver: a reply marked recursion available from a root server's address stops the lookup (closes #300)
resolver: a reply marked recursion available from a root server's address stops the lookup (closes #300)
Review: pass.
Model: opus-5-5
resolver: a reply marked recursion available from a root server's address stops the lookup (closes #300)
Rework, one point.
A refusal from a root server's address is not handled the way the ruling and the documents say. queryDNS (internal/resolver/iterative.go line 141) turns a REFUSED reply…