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

chore: libwaku - exposing discv5 store-client and relay connected and mesh peers #3003

Merged
merged 1 commit into from
Aug 29, 2024

Conversation

Ivansete-status
Copy link
Collaborator

@Ivansete-status Ivansete-status commented Aug 28, 2024

Description

Step further to make nwaku completely accessible from libwaku. Still pending to expose some features such as peer exchange, or filter.

Changes

  • Allow to start or stop discv5
  • Expose lightpush request operation
  • Expose list of connected and mesh peers
  • Expose store client

- Allow to start or store discv5
- Expose lightpush request operation
- Expose list of connected and mesh peers
- Expose store client
@Ivansete-status Ivansete-status self-assigned this Aug 28, 2024
@Ivansete-status Ivansete-status changed the title chore: libwaku - exposing more features chore: libwaku - exposing discv5 store-client and relay connected and mesh peers Aug 28, 2024
Copy link

You can find the image built from this PR at

quay.io/wakuorg/nwaku-pr:3003

Built from c808660

Copy link
Contributor

@gabrielmer gabrielmer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks so much!

Copy link
Contributor

@SionoiS SionoiS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM Thanks!

Comment on lines +454 to +455
if isNil(callback):
return RET_MISSING_CALLBACK
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this needed here but not in all other procs?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this needed here but not in all other procs?

Good point! Because some checks are left. I will submit an enhancement in a separate PR

@Ivansete-status Ivansete-status merged commit bd2cf99 into master Aug 29, 2024
14 of 16 checks passed
@Ivansete-status Ivansete-status deleted the complete-libwaku branch August 29, 2024 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants