4 Commits

Include renames

Author	SHA1	Message	Date
clawbot	087b8de9ae	Back off WHOIS lookups more slowly and stop asking for personal data (closes #159) ... A failed lookup now makes the fetcher's wait 1.5 times as long, up to one minute instead of five. A success still halves it. RIPE counts the person and role objects an answer holds against a daily limit per IP address, and refuses an address for good that passes it too often. RIPE, APNIC and AFRINIC are now asked with --no-personal, which leaves those objects out but keeps the organisation object. An answer with RIPE's access-denied or limit-reached error line is now reported as a refusal holding that line, not as an answer with no fields. Model: opus-5-5	2026-10-26 23:40:13 +01:00
clawbot	55ecb22846	Bound the WHOIS fetcher's success and error time lists (closes #118) ... recordSuccess and recordFailure appended a time on every fetch, and only GetStats, run when a stats endpoint is requested, dropped the times older than statsWindow, so a daemon nobody polled kept every one. Each now drops those times before it appends. The drop takes them off the front of the list instead of copying the rest: the times are in the order they were recorded, and it now runs on every fetch. The fetcher reads the time through a now field so a test can set the clock. The test records 100,000 successes and failures a second apart without asking for the stats and finds one hour's worth of each kept. Model: opus-5-5	2026-10-20 03:38:51 +02:00
clawbot	09d3073fa5	Bound each shutdown stage by the stop deadline (closes #100) ... Shutdown passes its context to every stage: the streamer, the four handlers, the WHOIS fetcher, the database maintainer and the HTTP server each stop waiting when it ends. A handler then skips its last write and logs how many updates it did not write, and the HTTP server closes the connections still open. The database is checkpointed and closed last, and left open once the deadline has passed, since a write may still hold it. The stop hook gives Shutdown 8 seconds and fx 9, inside the 10 seconds upaas and docker stop allow, so a stop signal exits 0. Model: opus-5-5	2026-10-20 02:15:10 +02:00
clawbot	abdc327c4c	Retry a WHOIS lookup that failed instead of storing it as complete (closes #105) ... A lookup whose RIR query failed, or whose RIR answer carried none of the WHOIS fields (a refusal of service, for one), returned IANA's answer as a success. The fetcher stored it as complete with blank fields, did not look the AS up again for 30 days, and shortened its interval. Such a lookup is now an error: the fetcher backs off and leaves the row as it was. The fields are read from the RIR's answer alone. An AS IANA refers to no RIR is stored with no WHOIS data, so it is not looked up again until it is stale, counting as neither a success nor a failure. Tests reach fake WHOIS servers through the client's DialContext. Model: opus-5-5	2026-10-20 00:02:34 +02:00