You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the waku E2E call it was mentioned that status-go already supports this feature (there's a DB setting for it). A test should be done to determine what's the current behavior of status-go when attempting to retrieve messages from such large period of time.
For making it easier to monitor the queries as they're received in the storenodes, in wakuv2/waku.go in the Query function (line 1082), the requestID can be hardcoded with some known value, so we can filter by it in kibana.
cc: @John-44 @cammellos @jm-clius @LNSD
During the waku E2E call it was mentioned that status-go already supports this feature (there's a DB setting for it). A test should be done to determine what's the current behavior of status-go when attempting to retrieve messages from such large period of time.
For making it easier to monitor the queries as they're received in the storenodes, in
wakuv2/waku.go
in theQuery
function (line 1082), the requestID can be hardcoded with some known value, so we can filter by it in kibana.The text was updated successfully, but these errors were encountered: