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

Correct the length of a year #2025

Closed
wants to merge 1 commit into from
Closed

Correct the length of a year #2025

wants to merge 1 commit into from

Conversation

coopr
Copy link
Contributor

@coopr coopr commented Jan 27, 2017

A year was incorrectly assumed to have 360 days. This change assumes a year has 365 days.

Note: new features are to be opened against next, hotfixes against master.

Issues resolved

Fix #2021

A year was incorrectly assumed to have 360 days. This change assumes a year has 365 days.
Copy link
Member

@thibaultcha thibaultcha left a comment

Choose a reason for hiding this comment

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

Hi,

Thanks for looking into this!

I believe this change should also be applied to the rate-limiting plugin, see https://github.com/Mashape/kong/blob/master/kong/plugins/rate-limiting/policies.lua#L20


Thanks for providing some detailed info in the body section. For the next time, please follow the instructed branches naming and commit message format as found in the CONTRIBUTING.md's Submitting a Pull Request section (we follow the Angular template). Linking to related GH issues in the commit log message is also a good practice to enforce. Example:

fix(rate-limiting) correct length of a year

A year was incorrectly assumed to have 360 days. 
This change assumes a year has 365 days.

Fix #2021

@thibaultcha
Copy link
Member

Let's get this into 0.9.9 as well once completed @thefosk

@thibaultcha thibaultcha added the pr/changes requested Changes were requested to this PR by a maintainer. Please address them and ping back once done. label Jan 31, 2017
thibaultcha added a commit that referenced this pull request Feb 1, 2017
A year was incorrectly assumed to have 360 days.
This change assumes a year has 365 days.

Thanks Cooper Marcus for the initial fix.

Fix #2021
Replaces #2025
@thibaultcha
Copy link
Member

Another fix was pushed to master with the requested updates. Will be in 0.9.9.

@thibaultcha thibaultcha closed this Feb 1, 2017
@thibaultcha thibaultcha deleted the coopr-year-365 branch February 1, 2017 00:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/changes requested Changes were requested to this PR by a maintainer. Please address them and ping back once done.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

response rate limiting plugin year length is 360 days
2 participants