You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an issue for both the latest release (1.3.9) and master (d06be70), which don't pin the psycopg2-binary dependency.
To Reproduce
Create a fresh installation
Attempt to perform a database migration
Result:
[…]
File "/usr/local/lib/python3.8/site-packages/django/db/utils.py", line 101, in inner
return func(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/django/db/backends/postgresql/utils.py", line 6, in utc_tzinfo_factory
raise AssertionError("database connection isn't set to UTC")
AssertionError: database connection isn't set to UTC
This can be resolved by pinning psycopg2-binary to less than 2.9, until Janeway uses a version of Django from 3.1 onwards.
The text was updated successfully, but these errors were encountered:
Django 1.11.x fails to connect to PostgreSQL databases when using
psycopg2 2.9 onwards, due to a failing timezone-related assertion.
This also moves from psycopg2 to psycopg2-binary for Lando, which should
have no external effect.
Closesopenlibhums#2274.
Describe the bug
Django 1.11.x fails to connect to PostgreSQL databases when using psycopg2 2.9 onwards, due to a failing timezone-related assertion.
See upstream for discussion:
Janeway version
This is an issue for both the latest release (1.3.9) and master (d06be70), which don't pin the
psycopg2-binary
dependency.To Reproduce
Result:
This can be resolved by pinning psycopg2-binary to less than 2.9, until Janeway uses a version of Django from 3.1 onwards.
The text was updated successfully, but these errors were encountered: