-
Notifications
You must be signed in to change notification settings - Fork 53
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
feat: store v3 return pubsub topics #2676
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving, but I do think the comment below should be addressed.
@@ -56,6 +56,7 @@ type | |||
ArchiveResponse* = object | |||
hashes*: seq[WakuMessageHash] | |||
messages*: seq[WakuMessage] | |||
topics*: seq[PubsubTopic] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mmm. Wouldn't it be better to return seq[(message, topic)] to keep the 1:1 association explicit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At the archive driver lvl it's separate then you would use a tuple at the archive lvl then undo the tuple at the Store lvl.
I tried it. I does not make much sense.
You can find the image built from this PR at
Built from fe7fe3a |
You can find the image built from this PR at
Built from fe7fe3a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🤩
We got a segfault in CI but i can't reproduce locally. :| |
Will merge even with CI red as it's unrelated and the issue is being investigated. |
This PR is meant to unblock Waku Sync work.
Before Store v3 did not return the pubsub topics messages were sent on, now it does.
Follows updated vacp2p/rfc@5d69ab5