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.

Sign up for GitHub

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

Jump to bottom

Fixtures Result in Runtime Warnings while time zone support is active #131

Closed
michaelhiiva opened this issue Oct 12, 2020 · 0 comments · Fixed by #169
Closed

Fixtures Result in Runtime Warnings while time zone support is active #131

michaelhiiva opened this issue Oct 12, 2020 · 0 comments · Fixed by #169
Labels
bug Bugs in our AGAGD system. enhancement
Projects
Triage

Comments

@michaelhiiva
Copy link
Contributor

michaelhiiva commented Oct 12, 2020 •
edited

Summary of Bug

On new the creation of new local app container the following error results: RuntimeWarning: DateTimeField Member.last_changed received a naive datetime (2020-07-18 00:00:00) while time zone support is active. Application still runs; however, there may be future issues if there is a need for timezone support.

Steps to Reproduce the Behaviour

  1. docker-compose up

The Expected Behaviour

The scripts/make_fake_fixtures.py creates Django valid dates with timezone support which can be added to the database for local development.

References

Also there are a lot of:

RuntimeWarning: DateTimeField Member.last_changed received a naive datetime (2020-07-18 00:00:00) while time zone support is active.

which might be worth dealing with.
@michaelhiiva michaelhiiva mentioned this issue Oct 12, 2020
Merged
@michaelhiiva michaelhiiva added this to Needs Triage in Triage via automation Oct 26, 2020
@michaelhiiva michaelhiiva moved this from Needs Triage to Low Priority in Triage Oct 26, 2020
@michaelhiiva michaelhiiva self-assigned this Nov 18, 2020
@michaelhiiva michaelhiiva mentioned this issue Nov 23, 2020
Open
@michaelhiiva michaelhiiva mentioned this issue Mar 9, 2021
Open
@michaelhiiva michaelhiiva removed their assignment Mar 9, 2021
@duckpunch duckpunch mentioned this issue Apr 4, 2021
Merged
duckpunch added a commit to duckpunch/agagd that referenced this issue Apr 4, 2021
@duckpunch
Merge pull request #1 from duckpunch/beta
35987d8 
Fix warnings, add live reload, add beta root

* The warnings issue is usgo#131.  This PR doesn't fix all of them, but it fixes most.
* The first part of uwsgi touch reload has been added.  Second part would be to watch `*.py` and touch that file.
* Added a place to do development for issues like usgo#148.
@duckpunch duckpunch mentioned this issue Apr 4, 2021
Merged
@michaelhiiva michaelhiiva linked a pull request Apr 5, 2021 that will close this issue
Fix warnings, add live reload, add beta root #169
Merged
Triage automation moved this from Low Priority to Closed Apr 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Bugs in our AGAGD system. enhancement
Projects
Triage
  
Closed
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix warnings, add live reload, add beta root duckpunch/agagd
1 participant
@michaelhiiva