The commit bf01fb200777 ("luajit: bump new version") introduced the LUAJIT_USE_UBSAN option in LuaJIT. The patch propagates the CMake option ENABLE_UB_SANITIZER used in Tarantool to the LuaJIT build. Needed for #10145 NO_CHANGELOG=build NO_DOC=build NO_TEST=build (cherry picked from commit b58791cf532c5a76a6941221358ca007bc97a85b)

With enabled UndefinedBehavior Sanitizer runtime error like below is triggered: NO_WRAP $ UBSAN_OPTIONS=external_symbolizer_path=/usr/lib/llvm-13/bin/llvm-symbolizer:print_stacktrace=1 $ ./build/src/tarantool -e "require('varbinary').new()" /home/sergeyb/sources/MRG/tarantool/third_party/luajit/src/lib_ffi.c:710:14: \ runtime error: null pointer passed as argument 2, which is declared to never be null /usr/include/string.h:44:28: note: nonnull attribute specified here NO_WRAP This happened because in the varbinary constructor, the NULL pointer was passed to `ffi.copy()` and then to `memcpy()`, which is an undefined behaviour. The patch fixes that. Needed for #10145 NO_CHANGELOG=codehealth NO_DOC=codehealth NO_TEST=codehealth (cherry picked from commit 30179d44da65f835d81494ad63e86935f1c5aad0)

Fixes #10563 NO_DOC=The documentation on the website has correct command, this is a purely --help output problem. NO_CHANGELOG=This commit is not related to tarantool's behavior or public APIs. (cherry picked from commit 22e86d2ed3f5f36099cf143868619d1f0df611ac)

The testcase "http_client.sock_family:\"AF_UNIX\".test_follow_location" is flaky in each run of `release_clang_asan` and `debug_asan_clang` workflows. Disabling a single testcase does not help. The patch disables a group of testcases executed with Unix domain socket. Needed for #9854 NO_CHANGELOG=testing NO_DOC=testing (cherry picked from commit 8fae8004f79ecd555537960c60c6e646b037c4cc)

The patch fixes a warning produced by luacheck: NO_WRAP test/app-luatest/http_client_test.lua:27:8: Error prone negation: negation is executed before relational operator. test/app-luatest/http_client_test.lua:28:8: Error prone negation: negation is executed before relational operator. NO_WRAP Found by Luacheck 1.2.0. Closes #10037 NO_CHANGELOG=codehealth NO_DOC=codehealth NO_TEST=codehealth (cherry picked from commit 8fd37731b68e1e1d8e258ab919d65907d52ec764)

`test_engine.lua` actively uses error injections. Sometimes error injections remain enabled and triggered on test teardown. This leads to false positive test fails like below: NO_WRAP 2024-09-10 12:38:42.317 [1305] main/3502/WRK #3387/..test.fuzz.lua.test_engine I> Worker #3387 has finished. 2024-09-10 12:38:47.167 [1305] main/104/test_engine.lua/..test.fuzz.lua.test_engine I> TEARDOWN 2024-09-10 12:38:47.171 [1305] main/104/test_engine.lua wal.c:1327 E> ER_WAL_IO: Failed to write to disk 2024-09-10 12:38:47.174 [1305] main test_engine.lua:564 E> ER_WAL_IO: Failed to write to disk 2024-09-10 12:38:47.174 [1305] main F> fatal error, exiting the event loop NO_WRAP The patch disables error injection at the beginning of teardown. NO_CHANGELOG=testing NO_DOC=testing (cherry picked from commit be709c63b49df0ca5e52a015115c7c726cf416d6)

The function `console.listen` does not accept a path with duplicate slashes, so absolute paths were rejected. The patch fixes that by always using absolute paths to Unix socket. Follows up the commit 5d18b84e1e76 ("test: enable remote console for debug"). NO_CHANGELOG=testing NO_DOC=testing NO_TEST=testing (cherry picked from commit 89dd6f5c76c5427a297ee64c9b250950e66ac9bc)

On Tarantool shutdown first swim worker fiber is finished as managed on shutdown one. So later when swim is collected we got crash in swim_gc() because `event_handler` is NULL at this point. There is no worker fiber so we need to free swim synchronously. The issue was hidden because we do not call lua_close() earlier. It had little change to occur. Now it is revealed. Closes #10495 Part-of #10211 NO_TEST=covered by existing tests NO_DOC=bugfix (cherry picked from commit 3a343825213b7b3ea00ca7c0f04a16cde5599307)

Closes #10531 NO_DOC=testing NO_CHANGELOG=testing (cherry picked from commit 4bc191535803454a9485ca56f35281a205d466e2)

The remote console is enabled for debugging purposes. It can be helpful when Tarantool is stuck and one need an access to console to gather an additional information about Tarantool (like `fiber.info` output or anything else). NO_CHANGELOG=testing NO_DOC=testing (cherry picked from commit 5d18b84e1e763d617c123c3e7f6fa88210f6ae6d)