On 9/18/23 8:36 AM, bryan.kartzman@yu.edu wrote:
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?
The above errors have nothing to do with timestamps.
There are entries in the hyperkitty_thread table with starting_email_id
= 1365 and 1366, i.e., SELECT * FROM hyperkitty_thread WHERE starting_email_id in (1365, 1366);, but there are no entries in the
hyperkitty_email table with id = 1365 or 1366.
You could look at the thread_id for those entries in the hyperkitty_thread table and see if there are entries in the hyperkitty_email table with message_id_hash = those thread_id values. if those entries exist, you can fix this by altering the starting_email_id of those entries to the respective id values for those messages from the hyperkitty_email table.
If those messages don't exist in the hyperkitty_email table, you could just delete the offending entries from the hyperkitty_thread table.
As far as deleting archives is concerned, a Django superuser should have
a Delete Archive button on the top level Hyperkitty view for the list.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan