| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When this module was written, it wasn't possible to cancel or reschedule a
timer. Times have changed, and we should take advantage of those new methods.
This module becomes a very thin wrapper around util.timer now, but I'd argue
it's still a very common and useful concept/abstraction to have around.
Possible API change: this removes the 'last_reset' field of the watchdog. This
was never really intended as a public thing, and I can't find any code that
uses it, so I consider removal to be safe.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
return foo and foo() crops multiple return values to a single one, so
any second return values etc were last, mostly error details.
Introduced in 7e9ebdc75ce4
|
| | |
| |
| |
| |
| | |
This is useful when there's more than one channel binding in
circulation, since perhaps there will be varying support for them.
|
| | |
| |
| |
| | |
Don't think this is otherwise shown anywhere outside of debug logs
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
I.e. the subset of port:list() relevant to the specified module.
|
| | | |
|
| | |
| |
| |
| | |
Don't think we cause any such errors right now, but you never know!
|
| | |
| |
| |
| | |
Silences luacheck warning about the metatable being unused.
|
| | |
| |
| |
| | |
Added in luacheck 0.26.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
luacheck 0.26 considers the _ prefix as a hint that the variable or
argument is unused, then warns if they are used despite this.
We have several places where this prefix is used to avoid shadowing
another similarly named variable, resulting in many instances of this
warning.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
This lets it adjust the width of tables to the actual terminal width.
|
| | |
| |
| |
| |
| | |
Could arguably be implied by 'recipient-unavailable' since if it was
available, this error wouldn't happen.
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Sending stanzas with a remote session as origin when the stanzas have a
local JID in the from attribute trips validation in core.stanza_router,
leading to warnings:
> Received a stanza claiming to be from remote.example, over a stream authed for localhost.example
Using module:send() uses the local host as origin, which is fine here.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes #1758
Introduced in 1ea01660c79a
In e62025f949f9 to and from was inverted since it changed from acting on
a reply to acting on the original stanza (or a clone thereof)
Unsure of the purpose of this check, you don't usually send stanzas to
your own full JID. Perhaps guarding against routing loops?
The check was present in the original commit of mod_smacks,
prosody-modules rev 9a7671720dec
|
| | |
| |
| |
| | |
Cuts down on noise as well
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes #1757
These places seem to have been left since e62025f949f9
The logic around expected_h in should_ack() misbehaved, always comparing
with 0 + unacked instead of acked + unacked.
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| | |
This is now done in net.unbound itself
Turning it back on in the config may still cause the problem of entries
there masking the DNS values.
|
| | |
| |
| |
| | |
For consistency and easier correlation of session events.
|
| | |
| |
| |
| |
| | |
Those lines are long and the risk of mistakes if another one needs to be
added seems high, but lower when factored out like this.
|
| | |
| |
| |
| | |
Tells you if you make a typo like "gropchat" or so
|
| | |
| |
| |
| | |
Gets you nice error messages if you make a typo in with error_reply()
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a Linux(?) socket option that delays the accept signal until
there is data available to read. E.g. with HTTP this might mean that a
whole request can be handled without going back trough another turn of
the main loop, and an initial client <stream> can be responded to.
This may have effects on latency and resource use, as the server does
not need to allocate resources until really needed.
|
| | |
| |
| |
| |
| | |
Since it provides some protection and error handling in the form of
logging.
|
| | |
| |
| |
| | |
Reduces the side effects of wrapsocket()
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Requires a patch to LuaSocket adding this socket option,
https://github.com/lunarmodules/luasocket/pull/378
sysctl tweaks
net.ipv4.tcp_fastopen=3
net.ipv4.tcp_fastopen_blackhole_timeout_sec = 0
net.ipv4.tcp_fastopen_key=$(</proc/sys/kernel/random/uuid)
Disabled by default since it an advanced performance tweak unlikely to
be needed by most servers.
|
| |\| |
|
| | |
| |
| |
| | |
This error is an error, therefore it should be at the error level
|
| | |
| |
| |
| |
| | |
This mirrors the behaviour with net.dns and avoids the initialization
issue in #1737
|
| |\| |
|
| | |
| |
| |
| |
| |
| | |
Answers my recurring question of
> Using cert "certs/example.com.crt" from index
... for what?
|
| |\| |
|
| | |
| |
| |
| |
| |
| | |
Due to the dummy statistics provider (see core.statsmanager line 250)
having a metatable that allows infinite indexing where everything is
always the same table, which end up in suf() in the concatenation line.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Setting the .smacks field enables code paths that expects the queue to
be present. The queue is initialized in wrap_session_out(). With
opportunistic writes enabled this happens immediately on .sends2s(), so
the sending <enable> must happen before OR after these two lines, not in
the middle.
|
| | |
| |
| |
| |
| | |
This previously was considered an error because the module API Teal spec
did not document a return value from module:add_timer()
|
| | |
| |
| |
| | |
Since it's used in mod_cron
|
| |\| |
|
| | | |
|
| | | |
|
