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 retrynumber #269

Merged
merged 5 commits into from
Nov 15, 2022
Merged

Conversation

JingmaoYou
Copy link
Contributor

Description

Fix: rename config retrynumber to retry_number

Pull request type

Please check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

Checklist

  • Linter passes correctly
  • Add tests which fail without the change (if possible)
  • All tests passing
  • Extended the README / documentation, if necessary

Does this introduce a breaking change?

  • Yes
  • No

Further comments

config/config.go Outdated
@@ -39,7 +39,7 @@ var (

defaultMaxPayloadSize = ByteSize(1 << 50)

defaultRetryNumber = 0
defaultRetryNumber = 1
Copy link
Collaborator

Choose a reason for hiding this comment

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

why is the default value to 1? if you do that the behavior of chproxy will change after the update? If yes, it would be better to put it back to 0 then let the chproxy admin choose whether or not the feature should be active

Copy link
Contributor

Choose a reason for hiding this comment

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

I agree with @mga-chka. For the sake of test it's enough what you have done in config_test.go

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed @mga-chka , @Garnek20

@gontarzpawel gontarzpawel merged commit 0731b44 into ContentSquare:master Nov 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

3 participants