| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Since we don't currently have hooks that includes type and id here, we
need to check those attributes in the handlers.
|
|
|
|
|
|
|
|
|
|
|
| |
This is primarily something that happens with an internal query to
mod_mam, which calls origin.send() several times with results, leading
to the first such result being treated as the final response and
resolving the promise.
Now, these responses pass trough to the underlying origin.send(), where
they can be caught. Tricky but not impossible. For remote queries, it's
even trickier, you would likely need to bind a resource or similar.
|
|
|
|
|
|
| |
Per the unspoken internal standard of -1 as priority for most built-in
event handlers, since this makes it easy for 3rd party plugins to
override behavior by hooking at the default priority of 0.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This line was copied from mod_mam, where `origin.username` made sense,
less so here.
|
|
|
|
|
|
|
|
| |
This is becoming more common in XMPP as people experiment with a MIX-like
model where the bare JID joins a group chat instead of a full JID.
Specifically right now this is being added to help with processing
notifications from mod_muc_offline_delivery.
|
|
|
|
|
|
| |
The intent is to ensure 'ondisconnect' only gets called once, while
giving buffered outgoing data a last chance to be delivered via the
:close() path in case the connection was only shutdown in one direction.
|
|
|
|
|
|
|
|
| |
Before 22825cb5dcd8 connection attempts that failed (e.g. connection
refused) would be immediately destroyed. After, it would schedule
another write cycle and then report 'ondisconnect' again when failing.
Thanks Martin for reporting
|
|\ |
|
| |
| |
| |
| | |
Should ensure shutdown even if sockets somehow take a very long to get closed.
|
| |
| |
| |
| |
| | |
This should ensure that sockets get closed even if they are added after
the quit signal. Otherwise they may keep the server alive.
|
| |
| |
| |
| |
| |
| | |
lfs or WHAT
How did this even happen?
|
| | |
|
| |
| |
| |
| | |
Remember to remove the compatibility things in some future version
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
XEP-0045 states:
> Affiliations are granted, revoked, and maintained based on the user's
> bare JID, not the nick as with roles.
Therefore inclusion of a full JID in affiliation queries is invalid.
Thanks to Ge0rG and Poezio for discovering this issue.
|
| |
| |
| |
| | |
Seems to have happened in 6427e2642976, probably because of Meld
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Instead try to write any remaining buffered data. If the write attempt
also fails with "closed" then there's nothing we can do and the socket
is gone.
This reverts what appears to be a mistakenly included part of c8aa66595072
Thanks jonas’ for noticing
|
| |
| |
| |
| | |
Ref #1643
|
| | |
|
| |
| |
| |
| | |
It's basically deprecated
|
| |
| |
| |
| | |
The singulars are supposed to be deprecated
|
| |
| |
| |
| |
| | |
All 'net' providers generate a _port option which must be in the global
section, but this mistakenly also warns about these options as well.
|
| | |
|
| |
| |
| |
| |
| | |
Added in 03714861f8fc but it did not appear to be used anywhere until
offline message "handling" was added to mod_mam in 8141645e3865
|
| | |
|
| |
| |
| |
| |
| | |
Since this stanza-id was generated elsewhere in mod_mam, there should be
no need for normalization.
|
| |
| |
| |
| |
| | |
In order to allow monitoring. Especially as there's not much in the way
of hard numbers on how much space gets used.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously it was unclear whether "client port" was the port that the
client connected to, or from. I hereby declare that the client port is
the source port and the server port is the destination port.
Incoming and outgoing connections can be distinguished by looking at
the_server reference, which only incoming connections have.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Behaviour follows the same logic as string.sub (so yes, 1-indexed).
|
| | |
|
| |
| |
| |
| | |
In this case I need them for 227 import/export.
|
| |
| |
| |
| |
| | |
Error in util.human.units.format because of B(nil) when the global quota
is unset.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Before, maximum storage usage (assuming all users upload as much as they
could) would depend on the quota, retention period and number of users.
Since number of users can vary, this makes it hard to know how much
storage will be needed.
Adding a limit to the total overall storage use solves this, making it
simple to set it to some number based on what storage is actually
available.
Summary job run less often than the prune job since it touches the
entire archive; and started before the prune job since it's needed
before the first upload.
|
| |
| |
| |
| |
| | |
Other tests don't require a running prosody and I forgot to start it
when testing.
|
| |
| |
| |
| |
| |
| |
| | |
This uses the (experimental) observe.jabber.network API to
perform external connectivity checks. The idea is to complement
the checks prosodyctl can already do with a (nearly) complete
s2s/c2s handshake from a remote party to test the entire stack.
|
| |
| |
| |
| | |
And to follow existing naming practices better than 'legacy_ssl' did.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Following the style of other options like (c2s|s2s)_require_encryption,
s2s_secure_auth etc.
|
| |
| |
| |
| |
| |
| | |
Mirroring the c2s 'direct_tls'. Naming things is hard.
direct_tls_s2s_ports = { 5269+1 }
|
| |
| |
| |
| |
| | |
This could be done with multiplexing, or a future additional port
definition.
|