From 5ce3d152e3537412e539c8e5f456a1997bf77192 Mon Sep 17 00:00:00 2001 From: sneak Date: Thu, 5 Nov 2026 05:40:23 +0000 Subject: [PATCH] Use routetable.MaxWaitingOriginChanges in the prefix handler test The test now reads the exported limit instead of its own copy of the number. Model: deepseek-v4-pro --- .../routewatch/prefixhandler_originchanges_internal_test.go | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/internal/routewatch/prefixhandler_originchanges_internal_test.go b/internal/routewatch/prefixhandler_originchanges_internal_test.go index 99ec4af..1c434d2 100644 --- a/internal/routewatch/prefixhandler_originchanges_internal_test.go +++ b/internal/routewatch/prefixhandler_originchanges_internal_test.go @@ -14,10 +14,6 @@ import ( "git.eeqj.de/sneak/routewatch/internal/routetable" ) -// waitingOriginChangesLimit is the routing table's maxWaitingOriginChanges, -// which this package cannot read. -const waitingOriginChangesLimit = 100000 - // TestPrefixHandlerWritesOriginChanges hands a running prefix handler an // announcement and flushes. The flush must write the origin change to the // database. @@ -149,7 +145,7 @@ func TestPrefixHandlerLogsTheDroppedOriginChanges(t *testing.T) { &slog.HandlerOptions{Level: slog.LevelWarn})), } - announceManyPrefixes(h.table, waitingOriginChangesLimit+1) + announceManyPrefixes(h.table, routetable.MaxWaitingOriginChanges+1) h.flushBatch()