| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
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 `>`.
|
| |
| |
| |
| |
| | |
Didn't do the configurable defaults thing here because I was going to do
this, so that there's only one spot where it's done.
|
| |
| |
| |
| |
| |
| | |
Mostly just to have the defaults merged so you can e.g.
output:configure({maxdepth=1})
|
| |
| |
| |
| |
| |
| |
| | |
If nickname enforcement is enabled this would otherwise let you bypass
the join check in muc.lib by registering an invalid nickname and then
joining with any nickname, letting register.lib change it to the invalid
registered nick.
|
| |
| |
| |
| |
| |
| | |
This is meant to help trace down an issue where Prosody apparently
creates multiple conflicting SQL engines, causing problems especially
with SQLite3, e.g. #616 #784.
|
| | |
|
| |
| |
| |
| | |
Sometimes you wanna adjust the maxdepth or something.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This makes it much nicer to inspect Prosody internals.
Existing textual status messages from commands are not serialized to
preserve existing behavior. Explicit serialization of configuration is
kept in order to make it clear that returned strings are serialized
strings that would look like what's actually in the config file.
The default maxdepth of 2 seems ought to be an okay default, balanced
between showing enough structure to continue exploring and DoS-ing your
terminal.
Thanks to Ge0rG for the motivation to finally do this.
|
| |
| |
| |
| | |
This was explicit previously
|
| |
| |
| |
| | |
The return statements were lost in d95e083931d1
|
|\| |
|
| |
| |
| |
| | |
Meant to reduce user confusion over what's reloaded and not.
|
| |
| |
| |
| |
| | |
This ensures rules in mod_mam apply to some extent. Messages worth
archiving are probably worth sending to other clients.
|
| |
| |
| |
| | |
Ensures that all your clients know about sent messages that failed.
|
| | |
|
| | |
|
|\| |
|