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

fix: adapt comment to corresponding used value #4828

Merged
merged 2 commits into from
Sep 18, 2024

Conversation

martinconic
Copy link
Contributor

@martinconic martinconic commented Sep 17, 2024

Checklist

  • I have read the coding guide.
  • My change requires a documentation update, and I have done it.
  • I have added tests to cover my changes.
  • I have filled out the description and linked the related issues.

Description

Fixes 4823

Open API Spec Version Changes (if applicable)

Motivation and Context (Optional)

Related Issue (Optional)

Screenshots (if appropriate):

Copy link
Collaborator

@ldeffenb ldeffenb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why mention the 250 twice?

pkg/pullsync/pullsync.go Outdated Show resolved Hide resolved
@martinconic martinconic merged commit c47fc8a into master Sep 18, 2024
14 checks passed
@martinconic martinconic deleted the fix/comment-handle-max-chunks branch September 18, 2024 09:57
Copy link
Collaborator

@ldeffenb ldeffenb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let 'er rip!

@@ -51,7 +51,7 @@ const (
pageTimeout = time.Second
makeOfferTimeout = 15 * time.Minute
handleMaxChunksPerSecond = 250
handleRequestsLimitRate = time.Second / handleMaxChunksPerSecond // handle max 100 chunks per second per peer
handleRequestsLimitRate = time.Second / handleMaxChunksPerSecond // handle max `handleMaxChunksPerSecond` chunks per second per peer
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like that much better as it clarifies that the rate is per second per peer (the latter being important) while not being redundant about the actual value.

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.

Invalid (obsolete) comment in pullsync
4 participants