#6759 HyperKitty not showing comments of threads
Closed: Fixed 6 years ago Opened 6 years ago by srakitnican.

There is an issue with HyperKitty every now and then where replies and counter of replies are not shown correctly.

Opera_Snapshot_2018-03-03_061013_lists.fedoraproject.org.png

This particular thread from attachment titled "News in opencv package" [1] has more then one reply, yet HyperKitty shows the number of comments as 0, the number of participants as 1 (the original poster), yet is shows more then one participants in the list bellow.

This particular issue is not found only on this particular thread, but all the recent ones seems to be affected, yet some older ones seems not. "Unannounced soname bump (Rawhide): qpdf (libqpdf.so.18 -> libqpdf.so.21)" from 4 days ago is showing replies for me.

I would like to point out that this is not the first time this happened, @puiterwijk already fixed the same thing once. Not sure what the issue was.

Reference mailing list archive (updated couple of times a day): https://www.spinics.net/lists/fedora-devel/threads.html

[1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/TWUNXZ4C2CYR776RHGJMOJ4IKBP3BDGT/


Metadata Update from @kevin:
- Issue tagged with: lists

6 years ago

Note that this particular thread looks correct to me now. I wonder if there's some delay in the archiver updating this? Or it only does so on a longer scale (daily?).

Yeah, there may be some delay depending on the number of email that HyperKitty is processing at the moment. If you're viewing during a mass rebuild for example, the task queue is going to be filled with actions on the scm-commits list and that may introduce temporary incoherences such as this.

ok, so should we just close this and accept that sometimes counts will be behind?

I'd say yes, maybe in that case just login to the machine and check the async task queue length (which can be done by running /srv/webui/mini-scripts/check-hyperkitty-perf.sh, I should add that to the SOP)

ok. Sounds good.

Thanks for the report, sorry there wasn't more we could do to fix it.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Login to comment on this ticket.

Metadata