Age | Commit message (Collapse) | Author |
|
From XEP 0045:
“Note: the requirement to reflect the 'id' attribute was added in version
1.31 of this XEP. Servers following the new specification SHOULD advertise
that with a disco info feature of 'http://jabber.org/protocol/muc#stable_id'
on both the service domain and on individual MUCs, so that clients can check
for support.”
|
|
fix #3283
|
|
Otherwise we can imagine that two clients changing this value at the same
time would mix things up.
ref #3275
|
|
fix #3275
|
|
This reverts commit ba879a882e031d7b8503f78fe41d1210000c96ca.
|
|
This reverts commit d62ca9f87906be6f046fe9d07afb8bfb69c166e3.
|
|
|
|
|
|
|
|
|
|
|
|
ref #3273
|
|
ref #3273
|
|
fix #3273
|
|
|
|
fix #3339
|
|
|
|
|
|
|
|
fix #3337
Because apparently the IDs are not always incrementing. We still use them to
know the order of two messages that were received at the same second (in
this case, the ID will always be incrementing).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Because it’s only supported in gcc>=5.0
|
|
|
|
|
|
fix #3325
|
|
fix #3320
|
|
fix #3324
|
|
|
|
fix #3328
|
|
We check that the device and inode numbers are actually the same as the
JOURNAL_STREAM value, instead of just checking that the value exists.
This fixes the logger unit tests
|
|
|