A poll: "Delete this thread"
Hi,
If you have a locally installed mailman3 instance, could you try (as an administrator) to visit a thread in Hyperkitty and click "Delete this thread"? Does the thread get deleted, and you return to "Recently active discussions" and everything is fine?
Even just a few replies would indicate a pattern. That it's usually ok, for example.
I get a spinning wheel, and "Thread matching query does not exist." HyperKitty==1.3.9, PostgreSQL, Ubuntu 22.04, memcached, gunicorn.
On 2024-06-19 15:29:36 -0000 (-0000), Sam Darwin wrote:
If you have a locally installed mailman3 instance, could you try (as an administrator) to visit a thread in Hyperkitty and click "Delete this thread"? Does the thread get deleted, and you return to "Recently active discussions" and everything is fine?
Even just a few replies would indicate a pattern. That it's usually ok, for example.
I get a spinning wheel, and "Thread matching query does not exist." HyperKitty==1.3.9, PostgreSQL, Ubuntu 22.04, memcached, gunicorn.
I do it semi-regularly with the latest MM3 suite and it works normally for me, though the instance I manage is a container deployment built from Abhilash's Dockerfiles with (MariaDB backend and Apache reverse-proxying to a UWSGI URL on the loopback).
Jeremy Stanley
Hello,
On Wed, Jun 19, 2024 at 03:29:36PM -0000, Sam Darwin wrote:
If you have a locally installed mailman3 instance, could you try (as an administrator) to visit a thread in Hyperkitty and click "Delete this thread"? Does the thread get deleted, and you return to "Recently active discussions" and everything is fine?
I have installed mailman3 (from Debian bookworm) and imported a few lists, and I could delete two threads without problems as administrator.
I get a spinning wheel, and "Thread matching query does not exist." HyperKitty==1.3.9, PostgreSQL, Ubuntu 22.04, memcached, gunicorn.
Debian packages: mailman3 3.3.8-2~deb12u1 mailman3-web 0+20200530-2.1 (Hyperkitty 1.3.7)
PostgreSQL 15.
Thanks for the replies. Not yet a close match to what I have installed. Jeremy is using Dockerfiles. Marc is running mailman3-web from 4 years ago "20200530". I may need to dig into the code and attempt to debug, line by line. "Oh, of course, in your settings refresh_cache needs to be set to 1, you have it set to 0", or something obscure like that. Or who knows.
On Fri, Jun 21, 2024 at 5:46 PM Sam Darwin via Mailman-users < mailman-users@mailman3.org> wrote:
Thanks for the replies. Not yet a close match to what I have installed. Jeremy is using Dockerfiles. Marc is running mailman3-web from 4 years ago "20200530". I may need to dig into the code and attempt to debug, line by line. "Oh, of course, in your settings refresh_cache needs to be set to 1, you have it set to 0", or something obscure like that. Or who knows.
I am running the latest MM3 stable code, I believe, and I can delete a thread without any problems. Running in a virtualenv. Mailman 3.3.9, Postorius Version 1.3.10, HyperKitty version 1.3.8.
Mailman Core Version GNU Mailman 3.3.9 (Tom Sawyer)
Mailman Core API Version 3.1
Mailman Core Python Version 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC
11.4.0]
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
On 6/21/24 07:45, Sam Darwin via Mailman-users wrote:
Thanks for the replies. Not yet a close match to what I have installed. Jeremy is using Dockerfiles. Marc is running mailman3-web from 4 years ago "20200530". I may need to dig into the code and attempt to debug, line by line. "Oh, of course, in your settings refresh_cache needs to be set to 1, you have it set to 0", or something obscure like that. Or who knows.
I manage 3 production mailman 3 servers and a development server. All 4 are running the current (as of today) heads of the GitLab branches installed in a venv. The versions of some dependencies probably vary, but all use django_q2-1.6.2 one uses Django-4.2.11, two use Django-4.2.6 and one uses Django-4.1.13. They all use memcached as the cache backend.
I don't know what you mean by the refresh_cache setting as I have no information about such setting.
All 4 servers are able to delete threads in HyperKitty with no issues.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Besides "delete this thread" not working, the number of comments, participants, and unread messages were updating sporadically, rather than immediately. Can you guess what it was? Don't read any further, to avoid spoilers.
qcluster wasn't running. The scripts I based my current installation scripts on had omitted qcluster. But given the 100 other things being taken into account... it's worth automating. Ok, solved.
participants (5)
-
Jeremy Stanley -
Marc SCHAEFER -
Mark Sapiro -
Odhiambo Washington -
Sam Darwin