check / check (push) Canceled after 0s
The prefix handler's batch kept one update per prefix across all peers, chosen by timestamp. One routing change reaches many peers within a second, so most peers' announcements and withdrawals in a batch were dropped, and for updates in the same second the first one won. The batch now keeps the last update per prefix and peer, in the order the feed delivered them, so updates from every peer are applied. Tests cover two peers announcing, two peers withdrawing, and one peer announcing then withdrawing or withdrawing then re-announcing in the same second, and check the in-memory route count and prefix distribution against the route table. Model: opus-5-5