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

bug: Lightpush's publish type error #2253

Open
AlejandroCabeza opened this issue Nov 28, 2023 · 4 comments
Open

bug: Lightpush's publish type error #2253

AlejandroCabeza opened this issue Nov 28, 2023 · 4 comments
Assignees
Labels
bug Something isn't working effort/hours Estimated to be completed in a few hours

Comments

@AlejandroCabeza
Copy link
Contributor

Problem

WakuLightPushClient.publish fails with "dial failure" when peer is PeerId.

Impact

...

To reproduce

  1. Instantiate two Switch, one will act as serverSwitch and the other as clientSwitch.
  2. Instantiate a WakuLightPush and a WakuLightPushClient, using the respective switches.
  3. Send a publish request using serverSwitch.peerInfo.toRemotePeerInfo().peerId.
  4. The response will be a "dial failure".

In step 3, if using serverSwitch.peerInfo.toRemotePeerInfo(), it will be successful.

Expected behavior

The method works fine when sending a RemotePeerId instead of PeerId. That is weird given RemotePeerId contains PeerId, hence I expected the method to behave exactly the same.

nwaku version/commit hash

@AlejandroCabeza AlejandroCabeza added the bug Something isn't working label Nov 28, 2023
@gabrielmer gabrielmer added the effort/hours Estimated to be completed in a few hours label Jun 4, 2024
@gabrielmer gabrielmer self-assigned this Jun 7, 2024
@gabrielmer
Copy link
Contributor

@AlejandroCabeza is there a test/branch for this somewhere we can use to reproduce?

@AlejandroCabeza
Copy link
Contributor Author

AlejandroCabeza commented Jun 10, 2024

@AlejandroCabeza is there a test/branch for this somewhere we can use to reproduce?

It's been a bit so I can't anything extra aside from what I posted. You weren't able to reproduce it?

@gabrielmer
Copy link
Contributor

It's been a bit so I can't anything extra aside from what I posted. You weren't able to reproduce it?

I was looking for the specific piece of code where it is supposed to reproduce instead of writing it, which is very error prone. No worries then :))

In future cases I think it would be better to provide the code so we all run the same thing and are on the same page.

@AlejandroCabeza
Copy link
Contributor Author

It's been a bit so I can't anything extra aside from what I posted. You weren't able to reproduce it?

I was looking for the specific piece of code where it is supposed to reproduce instead of writing it, which is very error prone. No worries then :))

In future cases I think it would be better to provide the code so we all run the same thing and are on the same page.

Generally I tend to leave a test for these cases, I don't know why I didn't on this occasion 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working effort/hours Estimated to be completed in a few hours
Projects
Status: To Do
Development

No branches or pull requests

2 participants