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

Network ABI Testing #6123

Closed
danpaul000 opened this issue Sep 26, 2019 · 4 comments
Closed

Network ABI Testing #6123

danpaul000 opened this issue Sep 26, 2019 · 4 comments
Labels
locked issue stale [bot only] Added to stale content; results in auto-close after a week.
Milestone

Comments

@danpaul000
Copy link
Contributor

danpaul000 commented Sep 26, 2019

Network ABI testing is something we probably should consider for SLP1 QA as well. Right now we blindly break the binary interface between nodes, which makes backwards compatible software updates hard/impossible. We might not want to commit to an ABI yet but knowing that we just broke it would be very nice

  • We have two distinct means of generating binary/serialized interfaces, one in JS, one in Rust using bincode.
  • Input channels to nodes: RPC & gossip (Tyera/Trent)
  • Could use some fuzzing or other intense testing (Tyera)
  • Which sockets are we actually using compared to the standard recommendation or 8000-10000 UDP/TCP ports?
@danpaul000 danpaul000 self-assigned this Sep 26, 2019
@mvines mvines added this to the Supertubes v0.22.0 milestone Oct 14, 2019
@danpaul000
Copy link
Contributor Author

@mvines I haven't had any time to start work in this area. That might change before SLP1 drop dead, but seems unlikely. Should we pull in another resource here, or push out the due date?

@stale
Copy link

stale bot commented Jun 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale [bot only] Added to stale content; results in auto-close after a week. label Jun 2, 2021
@stale
Copy link

stale bot commented Jun 18, 2021

This stale issue has been automatically closed. Thank you for your contributions.

@stale stale bot closed this as completed Jun 18, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Apr 3, 2022

This issue has been automatically locked since there has not been any activity in past 7 days after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked issue stale [bot only] Added to stale content; results in auto-close after a week.
Projects
None yet
Development

No branches or pull requests

2 participants