Mon, 11 Jul 2022 19:07:38 +0200 compat: Remove handling of Lua 5.1 location of 'unpack' function
Kim Alvefur <zash@zash.se> [Mon, 11 Jul 2022 19:07:38 +0200] rev 12593
compat: Remove handling of Lua 5.1 location of 'unpack' function
Mon, 11 Jul 2022 17:32:13 +0200 Merge 0.12->trunk
Kim Alvefur <zash@zash.se> [Mon, 11 Jul 2022 17:32:13 +0200] rev 12592
Merge 0.12->trunk
Sun, 10 Jul 2022 16:10:29 +0200 luacheck: Set expected globals to Lua 5.4 + compat
Kim Alvefur <zash@zash.se> [Sun, 10 Jul 2022 16:10:29 +0200] rev 12591
luacheck: Set expected globals to Lua 5.4 + compat Requires luacheck 0.25.0
Mon, 27 Jun 2022 01:22:36 +0200 core.s2smanager: Don't remove unrelated session on close of bidi session 0.12
Kim Alvefur <zash@zash.se> [Mon, 27 Jun 2022 01:22:36 +0200] rev 12590
core.s2smanager: Don't remove unrelated session on close of bidi session Normally with bidi, any outgoing connection should be the same as the incoming, hence when closing a bidi connection it should be removed as a route to the remote server. However it is not guaranteed, a remote bidi-capable server might have decided to open a new connection for some reason. This can lead to a situation where there are two bidi connections, and the s2sout route is a locally initiated s2sout connection. In this case, such a s2sout connection should be kept. Noticed in a rare case where bidi has just been enabled on a running server, and something establishes new connections immediately when a connection is closed.
Fri, 08 Jul 2022 19:56:29 +0200 Merge 0.12->trunk
Kim Alvefur <zash@zash.se> [Fri, 08 Jul 2022 19:56:29 +0200] rev 12589
Merge 0.12->trunk
Mon, 30 May 2022 17:34:58 +0200 luacheck: Shut up (backports 3caff1f93520, ignores module deleted in trunk) 0.12
Kim Alvefur <zash@zash.se> [Mon, 30 May 2022 17:34:58 +0200] rev 12588
luacheck: Shut up (backports 3caff1f93520, ignores module deleted in trunk)
Fri, 08 Jul 2022 19:43:47 +0200 Merge 0.12->trunk
Kim Alvefur <zash@zash.se> [Fri, 08 Jul 2022 19:43:47 +0200] rev 12587
Merge 0.12->trunk
Fri, 08 Jul 2022 19:42:48 +0200 Backport 875f73ead4e8 8e4033213c62 to deal with luacheck 0.26 0.12
Kim Alvefur <zash@zash.se> [Fri, 08 Jul 2022 19:42:48 +0200] rev 12586
Backport 875f73ead4e8 8e4033213c62 to deal with luacheck 0.26
Fri, 08 Jul 2022 19:36:07 +0200 Merge 0.12->trunk
Kim Alvefur <zash@zash.se> [Fri, 08 Jul 2022 19:36:07 +0200] rev 12585
Merge 0.12->trunk
Fri, 08 Jul 2022 17:32:48 +0200 util.datamapper: Improve handling of schemas with non-obvious "type" 0.12
Kim Alvefur <zash@zash.se> [Fri, 08 Jul 2022 17:32:48 +0200] rev 12584
util.datamapper: Improve handling of schemas with non-obvious "type" The JSON Schema specification says that schemas are objects or booleans, and that the 'type' property is optional and can be an array. This module previously allowed bare type names as schemas and did not really handle booleans. It now handles missing 'type' properties and boolean 'true' as a schema. Objects and arrays are guessed based on the presence of 'properties' or 'items' field.
(0) -10000 -3000 -1000 -300 -100 -10 +10 +100 +300 tip