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.

Sign up for GitHub

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

Jump to bottom

Investigate throttling of validation functions #86

Closed
wemeetagain opened this issue Jun 15, 2020 · 6 comments
Closed

Investigate throttling of validation functions #86

wemeetagain opened this issue Jun 15, 2020 · 6 comments

Comments

@wemeetagain
Copy link
Member

Originally posted by @vasco-santos in #83

The go-libp2p-gossipsub implementation has a throttled state that a message can go to if too many messages get validated at once. What would this look like in our implementation?
@stale
Copy link

stale bot commented Jul 31, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the bot:stale label Jul 31, 2020
@stale
Copy link

stale bot commented Aug 7, 2020

This issue or pull request has been automatically been closed due to inactivity.

@stale stale bot closed this as completed Aug 7, 2020
@wemeetagain wemeetagain reopened this Aug 7, 2020
@stale
Copy link

stale bot commented Sep 22, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the bot:stale label Sep 22, 2020
@stale
Copy link

stale bot commented Sep 30, 2020

This issue or pull request has been automatically been closed due to inactivity.

@stale stale bot closed this as completed Sep 30, 2020
@twoeths twoeths reopened this Dec 5, 2020
@stale stale bot removed the bot:stale label Dec 5, 2020
@wemeetagain wemeetagain mentioned this issue Dec 5, 2020
Closed
@stale
Copy link

stale bot commented Jan 20, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the bot:stale label Jan 20, 2021
@stale
Copy link

stale bot commented Jan 31, 2021

This issue or pull request has been automatically been closed due to inactivity.

@stale stale bot closed this as completed Jan 31, 2021
@wemeetagain wemeetagain mentioned this issue Dec 2, 2021
Merged
fryorcraken pushed a commit to fryorcraken/js-libp2p-gossipsub that referenced this issue Aug 2, 2022
@achingbrain
chore: update project config (ChainSafe#86)
3251829
fryorcraken pushed a commit to fryorcraken/js-libp2p-gossipsub that referenced this issue Aug 2, 2022
@semantic-release-bot
chore(release): 3.0.4 [skip ci]
7a68b4b 
## [3.0.4](libp2p/js-libp2p-pubsub@v3.0.3...v3.0.4) (2022-08-01)

### Trivial Changes

* update project config ([ChainSafe#86](libp2p/js-libp2p-pubsub#86)) ([3251829](libp2p/js-libp2p-pubsub@3251829))

### Dependencies

* update it-length-prefixed and uint8arraylists deps ([ChainSafe#91](libp2p/js-libp2p-pubsub#91)) ([f295fce](libp2p/js-libp2p-pubsub@f295fce))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wemeetagain @twoeths