Fix: Date value out of range when changing default TIME_ZONE variable to another value#879
Open
jhonvidal wants to merge 1 commit into
Open
Fix: Date value out of range when changing default TIME_ZONE variable to another value#879jhonvidal wants to merge 1 commit into
jhonvidal wants to merge 1 commit into
Conversation
… to another value
Collaborator
Author
|
It looks like the Travis CI is stuck. |
Member
|
django-SHOP should be migrated towards Github actions anyway. Travis-CI is dead. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For example, when changing the value of TIME_ZONE="America/Caracas" in the configuration file (testshop/settings.py), the following error is reported when running the tests:
My solution is to increase the minimum date by 1 week and decrease the maximum date by 1 week, this way when they change the TIME_ZONE value it doesn't run a date out of range error. By applying this solution you can verify that all tests were satisfactory: