Matthew Wild <mwild1@gmail.com> [Sun, 19 Jan 2020 15:28:09 +0000] rev 10602
mod_posix: Support for command-line flags to override 'daemonize' config option
-D / --daemonize
-F / --no-daemonize
Matthew Wild <mwild1@gmail.com> [Sun, 19 Jan 2020 15:27:16 +0000] rev 10601
prosody/util.startup: Switch to parse_args() for --root and --config
Matthew Wild <mwild1@gmail.com> [Sun, 19 Jan 2020 15:26:22 +0000] rev 10600
util.startup: Add startup step for parsing command-line options
Kim Alvefur <zash@zash.se> [Thu, 16 Jan 2020 16:30:26 +0100] rev 10599
core.moduleapi: Hook correct event type in some cases
In rare cases, module.host can be a bare JID, in which case this test
did the wrong thing.
Kim Alvefur <zash@zash.se> [Wed, 15 Jan 2020 21:18:30 +0100] rev 10598
util.set: Fix equality metamethod in Lua 5.3
Kim Alvefur <zash@zash.se> [Wed, 15 Jan 2020 21:16:08 +0100] rev 10597
util.ip: Fix equality metamethod for Lua 5.3
Kim Alvefur <zash@zash.se> [Wed, 15 Jan 2020 21:08:01 +0100] rev 10596
util.array: Fix equality metamethod in Lua 5.3
Lua 5.2 only used the __eq metamethod if both operands have the same
__eq, but Lua 5.3 will pick one from either operands that has one as
long as both are tables.
This results in array() == {} and all sorts of odd behavior, including
array() == util.json.null.
<MattJ> I think [array() == {}] should have the same semantics as {} == {}
Kim Alvefur <zash@zash.se> [Wed, 15 Jan 2020 21:14:06 +0100] rev 10595
util.json: Test util.array integration
This is to expose how [] == json.null due to a change in Lua 5.3 with
how the equality metamethod is chosen.
Kim Alvefur <zash@zash.se> [Tue, 14 Jan 2020 23:39:47 +0100] rev 10594
util.array: Add a test case for a behavior change in Lua 5.3
In Lua 5.1 and 5.2 the __eq metamethod is not invoked if the other
argument is of a different metatable, but in Lua 5.3 it is.
Kim Alvefur <zash@zash.se> [Sun, 12 Jan 2020 20:36:21 +0100] rev 10593
net.server_epoll: Log error about missing *all* callbacks at 'error' level