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

ratelimiter: fixing rate limiter use #755

Merged
merged 1 commit into from
Feb 6, 2015
Merged

ratelimiter: fixing rate limiter use #755

merged 1 commit into from
Feb 6, 2015

Conversation

jbenet
Copy link
Member

@jbenet jbenet commented Feb 6, 2015

Use of the ratelimiter should be conscious of the ratelimiter's
potential closing. any loops that add work to ratelimiter
should (a) only do so if the rate limiter is not closed,
or (b) prevent limiter while work is added
(i.e. use limiter.Go(addWorkHere))

Use of the ratelimiter should be conscious of the ratelimiter's
potential closing. any loops that add work to ratelimiter
should (a) only do so if the rate limiter is not closed,
or (b) prevent limiter while work is added
(i.e. use limiter.Go(addWorkHere))
@jbenet jbenet added the status/in-progress In progress label Feb 6, 2015
@btc
Copy link
Contributor

btc commented Feb 6, 2015

do calls to Go contribute to the limit imposed by LimitedGo?

otherwise LGTM

jbenet added a commit that referenced this pull request Feb 6, 2015
ratelimiter: fixing rate limiter use
@jbenet jbenet merged commit 03c910f into master Feb 6, 2015
@jbenet jbenet deleted the fix-ratelimiter-use branch February 6, 2015 19:57
@jbenet jbenet removed the status/in-progress In progress label Feb 6, 2015
@aschmahmann aschmahmann mentioned this pull request Dec 1, 2021
80 tasks
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

Successfully merging this pull request may close these issues.

2 participants