XSF Discussion - 2018-06-06

  1. Neustradamus


  2. Seve/SouL

    Neustradamus, what do you mean?

  3. Seve/SouL

    Ah ok, it's related to the topic above, my bad :)

  4. Neustradamus

    There is a problem for the last newsletter, the date is same from the previous

  5. Neustradamus

    There is a problem for the last newsletter, the date is same that the previous

  6. jonasw

    Neustradamus, can you make a PR against https://github.com/xsf/xmpp.org/ please?

  7. Seve/SouL

    Neustradamus, thank you

  8. jonasw

    or alternatively, somebody from commsteam can do it :)

  9. jonasw

    I’ll hit merge asap

  10. jonasw


  11. Kev

    Is there a way to tell what Prosody is doing that's maxxing out eos?

  12. Zash

    debug logs?

  13. Kev

    Where do I find those?

  14. Zash

    /dev/null of course

  15. MattJ

    Kev, maxxing out CPU?

  16. Kev

    Ah, no, they're in the /var/log/prosody.

  17. Kev

    MattJ: 100% of a core, and the xmppd was unresponsive for minutes at a time in the Council meeting a moment ago.

  18. Kev

    Oh, and now it's recovered.

  19. Kev

    Back down to ~=0%

  20. MattJ

    Nothing unusual stands out

  21. MattJ

    Do we have monitoring graphs of eos?

  22. Ge0rG

    Does it have MAM?

  23. Zash

    worse, it has mod_muc_log

  24. Ge0rG

    Will that block for minutes?

  25. flow

    mam question: a query with both after and start 1. is invalid 2. returns the "biggest" result set or 3. returns all messages after the given message *and* after the given date?

  26. flow

    course this question also applies to 'before' and 'end'

  27. flow

    and is what xep313 ex11 does

  28. MattJ

    flow, 3

  29. Zash

    flow: rsm navigates the subset defined by (start, end, with)