Closed fbarbu15 closed 2 months ago
As per our discussion with @chaitanyaprem, it seems that this happens because go-waku doesn't run metadata protocol on cluster-id
0.
This happens because named sharding has been deprecated in nwaku but not yet in go-waku. And we don't know if it will ever be, as the plan is to deprecate go-waku.
@fbarbu15 what do you think? should we close this bug? I don't think there's anything to do from nwaku side
yes, addressing it on the interop tests side
Problem
Seems that a breaking change was introduced that most of the nwaku -> go-waku interop tests are failing Also the go-waku store v3 tests are failing with a similar error
To reproduce
Connect 2 nodes (1 nwaku and 1 go-waku) and try to use waku features like lightpush, filter, relay Ex script:
nwaku version/commit hash
State the version of
nwaku
where you've encountered the bug or, if built off a specific commit, the relevant commit hash. You can check the version by running./wakunode2 --version
. harbor.status.im/wakuorg/nwaku:latest harbor.status.im/wakuorg/go-waku:latestAdditional context
Issue only reproduces on cluster id 0, if I use another cluster it will pass nwaku_and_gowaku_logs.zip