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

feat: parametrize courier worker #3601

Merged
merged 1 commit into from
Oct 30, 2023
Merged

feat: parametrize courier worker #3601

merged 1 commit into from
Oct 30, 2023

Conversation

aeneasr
Copy link
Member

@aeneasr aeneasr commented Oct 30, 2023

Allows one to parametrize how many messages the courier will fetch and how often it will fetch messages.

Related issue(s)

Checklist

  • I have read the contributing guidelines.
  • I have referenced an issue containing the design document if my change
    introduces a new feature.
  • I am following the
    contributing code guidelines.
  • I have read the security policy.
  • I confirm that this pull request does not address a security
    vulnerability. If this pull request addresses a security vulnerability, I
    confirm that I got the approval (please contact
    [email protected]) from the maintainers to push
    the changes.
  • I have added tests that prove my fix is effective or that my feature
    works.
  • I have added or changed the documentation.

Further Comments

Allows one to parametrize how many messages the courier will fetch and how often it will fetch messages.
Comment on lines +80 to +81
ViperKeyCourierWorkerPullCount = "courier.worker.pull_count"
ViperKeyCourierWorkerPullWait = "courier.worker.pull_wait"
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't this rather be poll?

Copy link
Member Author

Choose a reason for hiding this comment

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

Hm I think polling is more when you ask a server / component whether they're ready periodically, and pulling refers to retrieving data and altering state. But really I don't care either way :)

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, both would work in this case I think...

@codecov
Copy link

codecov bot commented Oct 30, 2023

Codecov Report

Merging #3601 (76a146d) into master (9c608b9) will increase coverage by 0.01%.
The diff coverage is 100.00%.

❗ Current head 76a146d differs from pull request most recent head 0252dd6. Consider uploading reports for the commit 0252dd6 to get more accurate results

@@            Coverage Diff             @@
##           master    #3601      +/-   ##
==========================================
+ Coverage   78.21%   78.22%   +0.01%     
==========================================
  Files         341      341              
  Lines       23136    23142       +6     
==========================================
+ Hits        18095    18103       +8     
  Misses       3686     3686              
+ Partials     1355     1353       -2     
Files Coverage Δ
courier/courier.go 72.22% <100.00%> (+0.79%) ⬆️
courier/courier_dispatcher.go 67.50% <100.00%> (+0.41%) ⬆️
driver/config/config.go 83.42% <100.00%> (+0.09%) ⬆️

... and 2 files with indirect coverage changes

@aeneasr aeneasr merged commit 0e4be57 into master Oct 30, 2023
@aeneasr aeneasr deleted the config-mail-queue branch October 30, 2023 14:25
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