| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | | |
Goal is to call this if the connection is using Direct TLS, either via
multiplexing or a future Direct TLS S2S port.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Global modules aren't quite considered loaded onto hosts, which
causes confusion in some cases. They are also reported in the log as
being served on http://*:5280/foo which is also a bit confusing, and
can't be clicked.
Global modules also have to have their paths configured in the global
section, which could be confusing and unexpected.
This global+shared method should be the best of both worlds.
|
| | |
| | |
| | |
| | | |
(thanks mjk)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Examples in XEP-0060 suggest that items should be listed in
chronological order, but we get them from the archive in reverse
order.
However when requesting specific items by id the results keep that
order and we don't want to flip it again.
At some point it would likely be best to use the archive API directly
instead of this util.cache-compatible wrapper.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Hopefully this will eventually be upgraded to RSM, which is why the
argument is called 'resultspec' and is a table.
|
| | |
| | |
| | |
| | | |
As suggested by RFC 7590
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Should no longer be used by anything since the conversion of mod_offline
to the archive API in 0.10.0, which was 4 years ago. The line clearing
the property is left for a bit longer in case someone has very old
offline messages or archived data.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
To be removed in the future, but not right now. Give the log warning a
chance to prod anyone who might have network_backend="select" in their
config first.
There's also things built on Verse which uses server_select.lua, which
will need to be updated somehow.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously it would have gone for server_select if util.poll was for
some reason not available, which should be never these days. And even if
it was, best to flush it out by throwing loud errors so users notice.
Then they can work around it by using select until we delete that one.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes that selecting libevent when unavaibalbe would fall back to select
instead of epoll, even if that's available.
This way, we only have to update it in once place when choosing a new
default.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In a case like this the timer would not be readded:
addtimer(1, function(t, id)
stop(id)
return 1
end);
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
MattJ on 09:34:24
> Zash: I think as a first step, offline messages should not be sent to
> clients that request MAM
https://chat.modernxmpp.org/log/modernxmpp/2021-08-31#2021-08-31-8518a542bd283686
|
| | |
| | |
| | |
| | |
| | |
| | | |
Otherwise a message archived by a remote server would be incorrectly
silently discarded. This should be safe from spoofing thanks to
strip_stanza_id earlier in the event chain.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Along with the previous commit, allows building the XML thing yourself,
should you wish to send it yourself or use it in a different context than
an iq reply.
API change: The 'reply' is removed from the event.
|