Alex Nazaruk 5fba77f295 fix(nntpd): support open-ended NNTP ranges in XOVER/OVER ... parseRange split the spec on '-' and required BOTH bounds to parse as integers. For a valid open-ended range like '5-' (RFC 3977 6.2.3 / RFC 2980 XOVER: article 5 through the last) strconv.ParseInt('') fails, so parseRange returned (0, 0) and handleOver asked the backend for articles in [0, 0] — zero rows. '-10' (first..10) was likewise broken. Treat an empty bound as the extreme (low 0 / high MaxInt64) while still returning an empty range for genuinely malformed specs. Add table-driven tests for the open-ended and malformed forms.		2026-07-02 23:01:10 +02:00
..
range_test.go	fix(nntpd): support open-ended NNTP ranges in XOVER/OVER	2026-07-02 23:01:10 +02:00
server.go	fix(nntpd): support open-ended NNTP ranges in XOVER/OVER	2026-07-02 23:01:10 +02:00
server_test.go	Fix NNTP IHAVE missing message ID (#24)	2026-06-15 01:34:13 -07:00