Some cursors are returning this error, while some are working fine. It looks like a 50% of the cursors are affected
To reproduce
If you can reproduce the behavior, steps to reproduce:
Have 4 messages in the store
Send a store v3 request with page size 2. Ex response:
{"requestId":"","statusCode":200,"statusDesc":"OK","messages":[{"messageHash":{"data":"Y/RQpwaGT4M5avLAo6n2zDbPBHD0fUwjf2vUHYjp0qs="}},{"messageHash":{"data":"oKge3KvFaY2GV5FVvtDY+rKxFR+u+0UnlZ+emeQqhkc="}}],"paginationCursor":{"data":"oKge3KvFaY2GV5FVvtDY+rKxFR+u+0UnlZ+emeQqhkc="}}
Retrieve the paginationCursor from the response and use it in a new request. Ex request:
curl -v -X GET "http://127.0.0.1:48915/store/v3/messages?cursor=oKge3KvFaY2GV5FVvtDY%2BrKxFR%2Bu%2B0UnlZ%2BemeQqhkc%3D&pageSize=100&ascending=true&pubsubTopic=%2Fwaku%2F2%2Frs%2F0%2F0" -H "Content-Type: application/json"
Actual behavior
In 50% of the cases I get 400 Bad Request with waku message hash parsing error: Incorrect base64 string
Problem
Some cursors are returning this error, while some are working fine. It looks like a 50% of the cursors are affected
To reproduce
If you can reproduce the behavior, steps to reproduce:
{"requestId":"","statusCode":200,"statusDesc":"OK","messages":[{"messageHash":{"data":"Y/RQpwaGT4M5avLAo6n2zDbPBHD0fUwjf2vUHYjp0qs="}},{"messageHash":{"data":"oKge3KvFaY2GV5FVvtDY+rKxFR+u+0UnlZ+emeQqhkc="}}],"paginationCursor":{"data":"oKge3KvFaY2GV5FVvtDY+rKxFR+u+0UnlZ+emeQqhkc="}}
curl -v -X GET "http://127.0.0.1:48915/store/v3/messages?cursor=oKge3KvFaY2GV5FVvtDY%2BrKxFR%2Bu%2B0UnlZ%2BemeQqhkc%3D&pageSize=100&ascending=true&pubsubTopic=%2Fwaku%2F2%2Frs%2F0%2F0" -H "Content-Type: application/json"
Actual behavior
In 50% of the cases I get 400 Bad Request with
waku message hash parsing error: Incorrect base64 string
Expected behavior
Should work
nwaku version/commit hash
harbor.status.im/wakuorg/nwaku:latest
Additional context
Cursors that work:
Cursors that doesn't work:
Logs:
node.log