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

Collator Protocol Revamp: Testing tools #7753

Open
alindima opened this issue Feb 28, 2025 · 7 comments
Open

Collator Protocol Revamp: Testing tools #7753

alindima opened this issue Feb 28, 2025 · 7 comments

Comments

@alindima
Copy link
Contributor

Tools for testing:

  1. connection exhaustion. We need to be able to spawn hundreds of connections ideally on a single machine. Let's first try by spawning a large number of regular test collators. If it doesn't work, we may need a custom stripped-down tool with minimal overhead.
  2. Providing invalid collations. We don't need such a large scale for this.
  3. Advertising but timing out during fetching (or slow loris). We also don't need very large scale for this.
@alindima alindima converted this from a draft issue Feb 28, 2025
@alindima alindima changed the title Draft: Testing tools Collator Protocol Revamp: Testing tools Feb 28, 2025
@MrishoLukamba
Copy link
Contributor

I am taking it @alindima @skunert

@alindima
Copy link
Contributor Author

@MrishoLukamba sorry, all of these collator protocol revamp issues are quite complex and not ready to be taken over by someone else yet

@MrishoLukamba
Copy link
Contributor

@MrishoLukamba sorry, all of these collator protocol revamp issues are quite complex and not ready to be taken over by someone else yet

Sure but I wanna get involved In solving it piece by piece. As I do understand enough to start on it.

@alindima
Copy link
Contributor Author

The design of the project is still work in progress, these are still draft tickets.

@bkchr
Copy link
Member

bkchr commented Feb 28, 2025

@alindima why are all of these individual tickets, if they are all in "draft" stage?

@alindima
Copy link
Contributor Author

alindima commented Mar 3, 2025

@alindima why are all of these individual tickets, if they are all in "draft" stage?

They are legitimate issues that will be worked on, but the implementation details are not all fleshed out, therefore not immediately actionable by someone else (not without significant guidance)

@bkchr
Copy link
Member

bkchr commented Mar 3, 2025

Maybe then you should keep them as draft :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

3 participants