Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

waku2: test behavior of query retrieval mechanism when the sync period is 30d #3064

Open
richard-ramos opened this issue Jan 10, 2023 · 0 comments

Comments

@richard-ramos
Copy link
Member

richard-ramos commented Jan 10, 2023

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 the Query function (line 1082), the requestID can be hardcoded with some known value, so we can filter by it in kibana.

	opts = append(opts, store.WithRequestId(requestID))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants