Post B5a20a9PnBHt7jntIW by puniko@mk.absturztau.be
 (DIR) More posts by puniko@mk.absturztau.be
 (DIR) Post #B5YlzhlmBhMi2SLYq8 by puniko@mk.absturztau.be
       0 likes, 0 repeats
       
       ok, so here is why the duplicate posts from local users in TLs happened:When something is posted, it creates a job "post-note" in the background queue. this job inserts the post in db, does a little magic on it, pushes it on the TLs and some other stuff and as the very last thing, it indexes it at the full text search provider. in my case, this was meilisearch. due to meilisearch being all wonky for some reason, it failed more often then not and in consequence failed the job to finish successfully. hence the job got requeued again in the delayed state.it then got picked up again, to run all over agian, causing the post to be resend to the TLs again and so on.i switched the full text search provider in config this afternoon and the dups are gone since then.issue on gitlab is updated, and i kept it open because i think a failed indexing shouldn't cause the job to be rescheduledsorry, it took me a while to figure this one out ​:neocat_googly_woozy:​
       
 (DIR) Post #B5YmMsYKGLRk8s6bse by fabos@der.cyberterror.ist
       0 likes, 0 repeats
       
       @puniko@mk.absturztau.be you've done a nice job puniko ​:neofox_heart:​
       
 (DIR) Post #B5YmtLNccPyQobZzAe by puniko@mk.absturztau.be
       0 likes, 0 repeats
       
       @fabos@der.cyberterror.ist ​:neocat_googly_woozy:​ honestly it was one of those its-right-in-front-of-me-but-i-cant-see-it things
       
 (DIR) Post #B5YqeE0q809RREyAnQ by bruchpilot@mk.absturztau.be
       0 likes, 0 repeats
       
       @puniko Good job, puni
       
 (DIR) Post #B5Yqku5mac63gSSxyi by fabos@der.cyberterror.ist
       0 likes, 0 repeats
       
       @puniko@mk.absturztau.be you were persistent and so you found it ​:neofox_3c:​
       
 (DIR) Post #B5YqkuFhzi2KBF6tRw by puniko@mk.absturztau.be
       0 likes, 0 repeats
       
       @fabos@der.cyberterror.ist ​:neocat_googly_woozy:​ i mean, i couldn't keep it going like that, could i. it was a rather annoying bug
       
 (DIR) Post #B5a20ZqytiXgCZBAZ6 by lyli@mk.absturztau.be
       0 likes, 0 repeats
       
       @puniko I see 2 issues, the msg being rescheduled, and the search provider being unable to index. (Bad formatting?)
       
 (DIR) Post #B5a20a9PnBHt7jntIW by puniko@mk.absturztau.be
       0 likes, 0 repeats
       
       @lyli the search provider not being able to index is not a sharkey issue but one of the search provider. sharkey rescheduling the job on index fail is tho