XMPP Service Operators - 2023-10-23


  1. lovetox

    hi operators, i want to inform you we investigate a bug in ejabberd 23.10 regarding bookmarks/pubsub ( https://github.com/processone/ejabberd/issues/4106 ), if this turns out to be indeed a server bug it means, bookmarks are broken, and your users may not be happy.

  2. Licaon_Kter

    lovetox: https://github.com/processone/ejabberd/commit/f48275bc112b123bb632cbd8fa52e6330ed6ac66 would fix it afaik

  3. Licaon_Kter

    Was raised in ejabberd channel after release

  4. edhelas

    Is it only related to Bookmarks, and not other Pubsub nodes ?

  5. Licaon_Kter

    Not sure on the details sorry

  6. lovetox

    the commit message reads like a horrible workaround

  7. lovetox

    > Only care about pep bookmarks options when creating node from scratch

  8. edhelas

    https://github.com/processone/ejabberd/issues/3044#issuecomment-1775832114

  9. lovetox

    no, no, no, publish options need always be checked

  10. lovetox

    not only on creation

  11. edhelas

    I put a comment on the related ticket

  12. Licaon_Kter

    I've updated my comment too, but that's all I know, the devs might chime next

  13. Licaon_Kter

    ... In #4106

  14. lovetox

    Licaon_Kter, the commit you showed looks like a interal publish, i think its for conversion purpose

  15. lovetox

    if you publish something to private bookmarks, it calls a publish on pubsub to sync it or something

  16. lovetox

    so no this would not fix the problem i see

  17. lovetox

    because the solution here was to not pass publish options, i dont have that luxury

  18. Licaon_Kter

    lovetox: yeoh specific for Https://docs.ejabberd.im/developer/ejabberd-api/admin-api/#bookmarks-to-pep

  19. Licaon_Kter

    Maybe you see some other deeply rooted issue

  20. ␀ Array

    hello!

  21. array

    hello!

  22. emus

    Dear operators, please start testing: https://certwatch.xmpp.net/

  23. neox

    emus, great !

  24. emus

    Leys thank to XSF Infrastructure team

  25. emus

    Lets thank to XSF Infrastructure team

  26. neox

    emus, I obtain 502 when testing :/

  27. neox

    Oh trying again I get a result

  28. neox

    Well, quite unstable xD

  29. oxpa

    xsf ftw =)

  30. singpolyma

    502 is surprising, i can look into it. It's definitely early testing I wrote this in the last two evenings

  31. MattJ

    I had a 502 as well, and then it took several attempts over minutes to eventually render a page

  32. singpolyma

    Must be crashing the web process, I'll check it once kids are in bed

  33. singpolyma

    Seems it was an issue with my watchdog. Should be fixed now