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

Future work #30

Open
2 of 5 tasks
seemenkina opened this issue Dec 28, 2024 · 0 comments
Open
2 of 5 tasks

Future work #30

seemenkina opened this issue Dec 28, 2024 · 0 comments
Assignees

Comments

@seemenkina
Copy link
Contributor

seemenkina commented Dec 28, 2024

CI

  • Сonfigure CI so that it can be tested from the local Waku Node

Benchmarks

  • Make measurements for adding a user: starting from the moment the user considers the admin key until he updates his group key. I think you can reuse the code from the tests:
    async fn join_group_flow(alice: &mut User, bob: &mut User, group_name: String) -> UserAction {
  • Make measurements for deleting a user: starting from the moment when a commit for deletion is generated until the moment when the commit is applied

Waku integration

  • Сheck that PoC works with more than one Waku node
  • Investigate why always get 2 messages from Waku here:
    waku_set_event_callback(move |signal| {
    . The problem is in the code, because the Waku logs show that one message is sent. So far I use a vector to store the last 30 messages and reject repeated messages, but it would be nice to understand what the problem is

Multiple admin stage

@seemenkina seemenkina self-assigned this Dec 28, 2024
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

No branches or pull requests

1 participant