| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This would help pinpoint if a crash happens during the handshake, which
has occurred a few times, e.g. like https://github.com/brunoos/luasec/issues/75
|
|
|
|
|
| |
This removes the need to disconnect and reconnect to the telnet console
for changes to take effect.
|
|\ |
|
| |
| |
| |
| | |
'when' field, fixes #1557
|
| |
| |
| |
| |
| | |
This led to a missing 'when' field on changed items, which would cause a
traceack.
|
| | |
|
| |
| |
| |
| | |
Because docs are good.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
While building a stanza there's a .last_add field keeping track of where
in the XML tree tags are being added. This field does not survive a
roundtrip through preserialize / deserialize. :reset() removes this,
which simplifes comparisons after such a roundtrip.
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The stanza-id added during archiving looks exactly like what should be
stripped, so the stripping must happen before archiving.
Getting priorities right is hard!
Also no test coverage yet.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is either dead code or actually a type error, but catching that
should be the responsibility of the session.send function. This type
check is left since everything after it assumes a stanza object.
These last few commits aren't meant to change any behavior and it did
mark things not stanzas as important, but those would have been mostly
raw strings which are now specially handled.
|
| |
| |
| |
| |
| |
| |
| | |
Single space character is sent by mod_c2s when a session has been
silent for some time. This should account for the vast majority of raw
strings passing through here. If this is not the case then having stats
to say otherwise will be interesting.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Telnet command `stats:show("buffer_hold"):histogram()` looks nice!
|
| |
| |
| |
| | |
It now matches other the other source of flush reason logging.
|
| |
| |
| |
| | |
For symmetry.
|
| |
| |
| |
| | |
Otherwise it might not start from zero when enabled again.
|
| |
| |
| |
| |
| |
| | |
Forgot to unset the flag afterwards, so it would only work once.
The flag is not even needed, it works as intended without it.
|
| |
| |
| |
| | |
Autocomplete fail probably.
|
| |
| |
| |
| |
| |
| | |
To make it easier to find implemented Experimental XEPs later. Also at
the time of this commit it has been Proposed as mentinoed in the
comment but hopefully that will be resolved soon.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
For similarity with mod_mam, mod_csi_simple
|
|\| |
|
| |
| |
| |
| |
| |
| | |
Improves experience with VoIP calls initiated via JMI
Closes #1548
|
| | |
|
| |
| |
| |
| | |
Nice typo
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`session:dispatch_stanza(pres)` enqueues processing of the stanza in the
sessions async thread, but becasue the entire stream close handling is
now in that thread it would process the presence after the stream and
session was completely closed, leading to weird errors "sent to a
resting session".
We call core_process_stanza() since this is what :dispatch_stanza calls
in the end.
|
| |
| |
| |
| |
| |
| |
| | |
Probably casued by mod_scansion_record catching the unavailable presence
generated by Prosody on disconnect.
See #1549
|
| |
| |
| |
| | |
Enables async processing during stream opening and closing.
|
| |
| |
| |
| |
| | |
Allows async processing during stream shutdown. Fixes potential ASYNC-01
issues, however no such issues known at the time of this commit.
|
| |
| |
| |
| | |
Makes it clearer, cleaner and easier to extend.
|
| | |
|
| |
| |
| |
| | |
Should improve quality of debug logs
|
| |
| |
| |
| |
| |
| | |
Same style as mod_mam and mod_carbons allows easy comparison.
BC: Log format changes
|
| |
| |
| |
| | |
Updates #1533
|
| | |
|
| | |
|
| |
| |
| |
| | |
The :find bit was hard to understand, this should be clearer.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A large share of `<presence type=error>` appears to be noise from large
public channels and failed presence probes. The later at least should
count as presence updates, which are currently considered unimportant.
See also 8cecb85e4bc4 which is partly reverted here. The intent there
was probably mostly about message (delivery) errors, which should be
considered important.
|
| |
| |
| |
| |
| |
| | |
With mod\_storage\_internal this counts out to 100 messages out of 10 000,
meaning should not hit the quota limit immediately until that many
messages have been added again.
|
| |
| |
| |
| |
| |
| |
| | |
Passing around PIDs, UIDs etc as integers makes it more sane in Lua 5.3.
Getting 1234.0 as PID is silly. Shouldn't change any behavior as these
are all integers on the C side and the integral floats are accepted as
integers when passed back from Lua into C.
|
| |
| |
| |
| |
| | |
This has some nice effects such as functions, VirtualHosts and other
things being printed using their `__tostring` metamethod.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Typing e.g. `c2s` would dump out a bunch of stuff that would probably
just confuse users.
Now you only get pretty-printing when poking around in the internals
with `>`.
|