-
Notifications
You must be signed in to change notification settings - Fork 307
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
Integrate the mock reactor and allow running it with a flag #1545
Comments
I would like to try to solve this issue as my first contribution @rach-id |
Awesome 🎉 ill assign you |
Hey, I noticed this issue is currently assigned. I was wondering if there’s still an opportunity to contribute to this or assist in any way. I'm interested and would be happy to collaborate or pick it up if it becomes available. Let me know! |
@abhirajprasad Here is a list of issues you can help with: core:
good first issue
app: https://github.com/celestiaorg/celestia-app/labels/good%20first%20issue |
Hello, I'm sorry for not being able to complete the assigned tasks on time. This was not the outcome I expected and I'm very sorry for it.Because I recently encountered an unexpected urgent task at work, I was unable to devote enough time to this project. @rach-id |
In order to do the investigation in #1385 (comment), we implemented a mock reactor that floods the network with random data to load test the P2P stack.
It would be good to take the mock reactor implementation from the branches mentioned in the comment above, polish it, then integrate it in v0.34.x branch.
Also, would be amazing to have a CLI flag,
--only-load-reactor
for example, that allows switching from a consensus network to just running the mock reactor to load test the P2P stack.The text was updated successfully, but these errors were encountered: