graph/db: let test policy have some extra opaque data
What the developer wrote
Authored by Elle Mouton
graph/db: let test policy have some extra opaque data
This will help us test idempotency later on, but it also ensures that
TestMigrateGraphToSQL is properly testing writes to the
graph_channel_policy_extra_types table.
What changed, and why it matters
This is a small test-only change that adds a field to a helper function used in database migration tests. It does not change any production code, network behavior, or user-facing functionality. There is no security issue here.
No action needed. This is a benign test-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit modifies graph/db/sql_migration_test.go, specifically the makeTestPolicy test helper, to populate the ExtraOpaqueData field of a ChannelEdgePolicy with testExtraData. The stated purpose is to improve test coverage for the graph_channel_policy_extra_types table and to support future idempotency tests. No runtime code is affected.
Changed components
graph/db/sql_migration_test.goInspect captured patch +1 / −0
diff --git a/graph/db/sql_migration_test.go b/graph/db/sql_migration_test.go
index c555e43..84f7e99 100644
--- a/graph/db/sql_migration_test.go
+++ b/graph/db/sql_migration_test.go
@@ -716,6 +716,7 @@ func makeTestPolicy(chanID uint64, toNode route.Vertex, isNode1 bool,
FeeBaseMSat: math.MaxUint64,
FeeProportionalMillionths: math.MaxUint64,
ToNode: toNode,
+ ExtraOpaqueData: testExtraData,
}
for _, opt := range opts {
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.