Mark,
Thanks. I just saw your response. I actually thought of that myself and converted all timestamp fields in the database to "with time zone" last week with the following code:
ALTER TABLE public.account_emailconfirmation ALTER COLUMN created TYPE TIMESTAMP WITH TIME ZONE USING created AT TIME ZONE 'EDT';
ALTER TABLE public.account_emailconfirmation ALTER COLUMN sent TYPE TIMESTAMP WITH TIME ZONE USING sent AT TIME ZONE 'EDT';
ALTER TABLE public.auth_user ALTER COLUMN last_login TYPE TIMESTAMP WITH TIME ZONE USING last_login AT TIME ZONE 'EDT';
ALTER TABLE public.auth_user ALTER COLUMN date_joined TYPE TIMESTAMP WITH TIME ZONE USING date_joined AT TIME ZONE 'EDT';
ALTER TABLE public.django_admin_log ALTER COLUMN action_time TYPE TIMESTAMP WITH TIME ZONE USING action_time AT TIME ZONE 'EDT';
ALTER TABLE public.django_migrations ALTER COLUMN applied TYPE TIMESTAMP WITH TIME ZONE USING applied AT TIME ZONE 'EDT';
ALTER TABLE public.django_q_ormq ALTER COLUMN lock TYPE TIMESTAMP WITH TIME ZONE USING lock AT TIME ZONE 'EDT';
ALTER TABLE public.django_q_schedule ALTER COLUMN next_run TYPE TIMESTAMP WITH TIME ZONE USING next_run AT TIME ZONE 'EDT';
ALTER TABLE public.django_q_task ALTER COLUMN started TYPE TIMESTAMP WITH TIME ZONE USING started AT TIME ZONE 'EDT';
ALTER TABLE public.django_q_task ALTER COLUMN stopped TYPE TIMESTAMP WITH TIME ZONE USING stopped AT TIME ZONE 'EDT';
ALTER TABLE public.django_session ALTER COLUMN expire_date TYPE TIMESTAMP WITH TIME ZONE USING expire_date AT TIME ZONE 'EDT';
ALTER TABLE public.hyperkitty_email ALTER COLUMN date TYPE TIMESTAMP WITH TIME ZONE USING date AT TIME ZONE 'EDT';
ALTER TABLE public.hyperkitty_email ALTER COLUMN archived_date TYPE TIMESTAMP WITH TIME ZONE USING archived_date AT TIME ZONE 'EDT';
ALTER TABLE public.hyperkitty_lastview ALTER COLUMN view_date TYPE TIMESTAMP WITH TIME ZONE USING view_date AT TIME ZONE 'EDT';
ALTER TABLE public.hyperkitty_mailinglist ALTER COLUMN created_at TYPE TIMESTAMP WITH TIME ZONE USING created_at AT TIME ZONE 'EDT';
ALTER TABLE public.hyperkitty_thread ALTER COLUMN date_active TYPE TIMESTAMP WITH TIME ZONE USING date_active AT TIME ZONE 'EDT';
ALTER TABLE public.postorius_emailtemplate ALTER COLUMN created_at TYPE TIMESTAMP WITH TIME ZONE USING created_at AT TIME ZONE 'EDT';
ALTER TABLE public.postorius_emailtemplate ALTER COLUMN modified_at TYPE TIMESTAMP WITH TIME ZONE USING modified_at AT TIME ZONE 'EDT';
ALTER TABLE public.socialaccount_socialaccount ALTER COLUMN last_login TYPE TIMESTAMP WITH TIME ZONE USING last_login AT TIME ZONE 'EDT';
ALTER TABLE public.socialaccount_socialaccount ALTER COLUMN date_joined TYPE TIMESTAMP WITH TIME ZONE USING date_joined AT TIME ZONE 'EDT';
ALTER TABLE public.socialaccount_socialtoken ALTER COLUMN expires_at TYPE TIMESTAMP WITH TIME ZONE USING expires_at AT TIME ZONE 'EDT';
I'd like to say it worked flawlessly (and it did allow the archives to be displayed, which wasn't happening before, but I'm getting the following two errors (or maybe KeyError 1365 and 1366 are the same error?) every minute:
11:26:23 [Q] ERROR Failed [compute_thread_positions] - 1365 : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 37, in walk_successors obj = graph.nodes[msgid]["obj"] File "/usr/lib/python3/dist-packages/networkx/classes/reportviews.py", line 187, in __getitem__ return self._nodes[n] KeyError: 1365
11:26:23 [Q] ERROR Failed [compute_thread_positions] - 1366 : Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django_q/cluster.py", line 421, in worker res = f(*task["args"], **task["kwargs"]) File "/usr/lib/python3/dist-packages/hyperkitty/tasks.py", line 127, in _compute_thread_positions compute_thread_order_and_depth(thread) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 55, in compute_thread_order_and_depth walk_successors(thread.starting_email.id) File "/usr/lib/python3/dist-packages/hyperkitty/lib/analysis.py", line 37, in walk_successors obj = graph.nodes[msgid]["obj"] File "/usr/lib/python3/dist-packages/networkx/classes/reportviews.py", line 187, in __getitem__ return self._nodes[n] KeyError: 1366
Is this an error only in the archives or might I also have a problem with other timestamp fields in the database? If its just the archives, is there a simple way to fix it? If no simple way to fix the archives, is there an easy way to erase all list archives? If no easy way to erase all list archives, would deleting all the lists and recreating them remove the archives?