clawbot 237f73fc49 Answer 500, not 404, when the IP lookup cannot read the database (closes #109) ...

A failed database read for an address was listed in the answer's errors
as if the address had no route, so the lookup answered 404, or 200 next
to a routed address. Only a missing route or an invalid address is
listed now; any other read error is logged and answers 500 with the JSON
error body, as the AS and prefix JSON routes do.

Model: opus-5-5

2026-10-20 01:49:34 +02:00

..

config

Add the HTTP hardening the policy requires before 1.0 (closes #108)

2026-10-20 01:36:18 +02:00

database

Checkpoint without waiting on readers and log a busy checkpoint (closes #102)

2026-10-20 01:06:51 +02:00

logger

Re-vendor the shared files from sneak/prompts at 0653579 (closes #52)

2026-10-19 12:10:11 +02:00

metrics

Let bgp_peer_count drop to 0 (closes #92)

2026-10-19 12:41:15 +02:00

ristypes

Keep a trailing AS set out of the origin and the peerings (closes #75)

2026-10-19 12:50:05 +02:00

routewatch

Checkpoint without waiting on readers and log a busy checkpoint (closes #102)

2026-10-20 01:06:51 +02:00

server

Answer 500, not 404, when the IP lookup cannot read the database (closes #109)

2026-10-20 01:49:34 +02:00

streamer

Drain the handler queues before stopping the handlers on shutdown (closes #69)

2026-10-19 13:08:48 +02:00

templates

Add the HTTP hardening the policy requires before 1.0 (closes #108)

2026-10-20 01:36:18 +02:00

version

Re-vendor the shared files from sneak/prompts at 0653579 (closes #52)

2026-10-19 12:10:11 +02:00

whois

Cap WHOIS answers and follow referrals only to WHOIS servers (closes #106)

2026-10-20 00:15:14 +02:00