bug: bridge-service: fails a call to /bridge/v1/claims?network_id=n if there are bridges with NULL data (pending to be filled)

[joanestebanr]

Bug Report

Version '0.8.1`

calling to https://host/bridge/v1/claims?network_id=n
returns:

upstream connect error or disconnect/reset before headers. reset reason: connection termination

Backlog

ERROR (1) <bridgesync/processor.go:1003>: GetClaimsPaged: meddler.ScanAll failed for pageNumber=1, pageSize=20: context deadline exceeded
    ts: 1772096739.0290687
    version: "v0.8.1"
    module: "L2BridgeSyncer"
    stacktrace: "github.com/agglayer/aggkit/bridgesync.(*processor).GetClaimsPaged\n\t/app/bridgesync/processor.go:1003\ngithub.com/agglayer/aggkit/bridgesync.(*BridgeSync).GetClaimsPaged\n\t/app/bridgesync/bridgesync.go:329\ngithub.com/agglayer/aggkit/bridgeservice.(*BridgeService).GetClaimsHandler\n\t/app/bridgeservice/bridge.go:526\ngithub.com/gin-gonic/gin.(*Context).Next\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.11.0/context.go:192\ngithub.com/agglayer/aggkit/bridgeservice.New.LoggerHandler.func1\n\t/app/bridgeservice/bridge.go:164\ngithub.com/gin-gonic/gin.(*Context).Next\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.11.0/context.go:192\ngithub.com/gin-gonic/gin.CustomRecoveryWithWriter.func1\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.11.0/recovery.go:92\ngithub.com/gin-gonic/gin.(*Context).Next\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.11.0/context.go:192\ngithub.com/gin-gonic/gin.(*Engine).handleHTTPRequest\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.11.0/gin.go:689\ngithub.com/gin-gonic/gin.(*Engine).ServeHTTP\n\t/go/pkg/mod/github.com/gin-gonic/gin@v1.11.0/gin.go:643\nnet/http.serverHandler.ServeHTTP\n\t/usr/local/go/src/net/http/server.go:3340\nnet/http.(*conn).serve\n\t/usr/local/go/src/net/http/server.go:2109"
WARN (1) <bridgeservice/bridge.go:528>: failed to get claims for L2 network (ID=20): context deadline exceeded
    ts: 1772096739.0291438
    version: "v0.8.1"
    module: "bridge"

Notes

This error was exposed at the same time that this issue: #1514 (maybe are related)
Link to the slack conversation

Additional context

Add any other context about the problem here.