It is convenient to access configuration using `config:get()` from the
application script (`app.file` or `app.module`).

However, before this commit, it was not possible, because the
configuration was not considered as applied before the application
script is loaded.

Now, the script loading is moved into the post-apply phase.

The resulting sequence of steps on startup/reload is the following.

* collect configuration information (from all the sources)
* <if the previous step is failed, set `check_errors` status and break>
* apply the configuration (call all the appliers)
* <if the previous step is failed, set `check_errors` status and break>
* <set the new successful status: `ready` or `check_warnings`>
* call post-apply hooks (including application script loading)
* <if the previous step is failed, set `check_errors` status and break>
* <set the new successful status: `ready` or `check_warnings`>

I would like to briefly comment the changes in the tests.

* `app_test.lua`: added the check for the new behavior (call
  config:get() from the app script)
* `appliers_test.lua`: fixed the applier call (`.apply` ->
  `.post_apply`)
* `config_test.lua`: fixed status observed in the app script
  (`*_in_progress` -> `ready`)

Part of #8862

NO_DOC=reflected in https://github.com/tarantool/doc/issues/3544

The declarative config has the `app` section with following three
parameters:

* `app.file` -- the path to the script file
* `app.module` -- the same, but the script is searched using the Lua
  search paths (and loaded using `require`)
* `app.cfg` -- a user provided configuration (arbitrary map)

This commit adds a few success/failure cases. The goal is to have simple
test examples to add more ones easier in a future.

Implemented several test helpers for typical scenarios that can be used
outside of the application script test.

Part of #8862

NO_DOC=testing improvements
NO_CHANGELOG=see NO_DOC

The usual environment configuration source is useful for parametrized
run:

```
TT_MEMTX_MEMORY=<...> tarantool --name <...> --config <...>
```

However, sometimes a user may need to set a default value, which doesn't
rewrite one that is provided in the configuration. Now, it is possible
to do using the environment variables with the `_DEFAULT` suffix.

```
TT_MEMTX_MEMORY_DEFAULT=<...> tarantool --name <...> --config <...>
```

This feature may be especially useful for wrappers that run tarantool
internally with some default paths for data directories, socket files,
pid file. We likely will use it in the `tt` tool.

Part of #8862

NO_DOC=added into https://github.com/tarantool/doc/issues/3544 manually

It simplifies code reusage in the following commit, which adds the
second environment config source.

Part of #8862

NO_DOC=no user-visible changes, just code refactoring
NO_CHANGELOG=see NO_DOC
NO_TEST=see NO_DOC

Bump test-run to new version with the following improvements:

- luatest: fix detect tarantool crash at exit [1]
- Fix bug when lua script name truncated by dot [2]
- Raise an error and log it if test timeouts are set incorrectly [3]
- Pin PyYAML version to 5.3.1 [4]
- Add ability to set path to executable file [5]
- Migrate tarantoolctl from tarantool repository [6]
- Fix test-run crash when default server is crashed [7]
- Disable reproduce content printing [8]

[1] tarantool/test-run@be693d1
[2] tarantool/test-run@a6405f1
[3] tarantool/test-run@d34ecb0
[4] tarantool/test-run@704420e
[5] tarantool/test-run@0a70001
[6] tarantool/test-run@ad43d8f
[7] tarantool/test-run@b31329e
[8] tarantool/test-run@31f0ced

NO_DOC=test
NO_TEST=test
NO_CHANGELOG=test

* ci: introduce testing workflow with sanitizers
* build: introduce LUAJIT_USE_ASAN option
* test: introduce test:done TAP helper
* memprof: remove invalid assertions
* ci: clean up workflow for exotic builds

Closes #5878

NO_DOC=LuaJIT submodule bump
NO_TEST=LuaJIT submodule bump
NO_CHANGELOG=LuaJIT submodule bump

The is_old compat option method is more reliable than comparing
the current option value to 'old' directly because it may be set to
'default', in which case we also have to check the default value.

Follow-up #8807

NO_DOC=refactoring
NO_TEST=refactoring
NO_CHANGELOG=refactoring

The is_new and is_old methods are the same for all compat options so
they should be defined in a metatable. A good thing about this change
is that it removes is_new and is_old from serialization:

* Before:

NO_WRAP
  tarantool> require('compat').yaml_pretty_multiline
  ---
  - is_new: 'function: 0x4175d6e8'
    is_old: 'function: 0x4175d790'
    brief: |
      Whether to encode in block scalar style all multiline strings or ones
      containing "\n\n" substring. The new behavior makes all multiline string output
      as single text block which is handier for the reader, but may be incompatible
      with some existing applications that rely on the old style.

      https://tarantool.io/compat/yaml_pretty_multiline
    current: default
    default: new
  ...
NO_WRAP

* After:

NO_WRAP
  tarantool> require('compat').yaml_pretty_multiline
  ---
  - current: default
    brief: |
      Whether to encode in block scalar style all multiline strings or ones
      containing "\n\n" substring. The new behavior makes all multiline string output
      as single text block which is handier for the reader, but may be incompatible
      with some existing applications that rely on the old style.

      https://tarantool.io/compat/yaml_pretty_multiline
    default: new
  ...
NO_WRAP

To achieve that, we have to remove the option name from the usage error
message but it seems to be okay because such errors shouldn't happen in
practice and the error message is clear enough to figure out what went
wrong.

Follow-up #8807

NO_DOC=refactoring
NO_CHANGELOG=refactoring

Run release build LTO testing inside a Docker container created from the
`tarantool/testing:ubuntu-jammy-clang16` image with Clang 16 installed.

Closes #318

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Run release build testing inside a Docker container created from the
`tarantool/testing:ubuntu-jammy-clang16` image with Clang 16 installed.

Closes #317

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

NO_DOC=build
NO_TEST=build
NO_CHANGELOG=build

Add code owners for CI-related script and
for github automation directory.

NO_CHANGELOG=no code changes
NO_TEST=no code changes
NO_DOC=no code changes

The instance config schema was modified in commit 8ee2b0d8
("config: start singleton instance in RW by default"): the `database.rw`
(boolean) parameter was replaced by the `database.mode` parameter (enum
of `ro` and `rw`).

However, in the same commit, the default mode of an instance that is the
only one in its replicaset was modified: it starts in the read-write
mode by default. As result, the parameter is actually unneeded in the
minimal configuration example.

These changes were not reflected in the 'instance not found' error
message, which contains the minimal configuration example. It is fixed
here.

Part of #8862
Follows up #8810

NO_DOC=nothing to document, it is just an error message
NO_CHANGELOG=see NO_DOC
NO_TEST=there is a test case in config-luatest/reload_test.lua that
        triggers the given error; it doesn't needs updating, because it
        checks the start of the error message

This patch reverts the temporary fix introduced in commit
53c94bc7 ("test: disable Lua JIT in
app-luatest/http_client_test") since the issues with invalid traces
generation for vararg functions are resolved, so JIT machinery can be
enabled back then.

Follows up #8718
Relates to #8516

NO_DOC=test
NO_CHANGELOG=test

In order to improve tests of Tarantool core
assign dedicated team to perform review of each
and every change.

NO_CHANGELOG=no code changes
NO_TEST=no code changes
NO_DOC=no code changes

The following box.cfg options were described in instance_config
with defaults similar to ones in box.cfg:
* auth_type
* auth_delay
* disable_guest
* password_lifetime_days
* password_min_length
* password_enforce_uppercase
* password_enforce_lowercase
* password_enforce_digits
* password_enforce_specialchars
* password_history_length

Part of #8861

NO_DOC=tarantool/doc#3544 links the most actual schema,
       no need to update the issue.

Applier thread uses lsregion to allocate the messages for tx thread. The
messages are freed upon return to the applier thread using a
corresponding lsr_id.

Due to a typo, one of the lsregion allocations was made with a postfix
increment of lsr_id instead of the prefix one. Essentially, part of a
new message was allocated with an old lsr_id, and might be freed early
by a return of a previous message.

Fix this.

Closes #8848

NO_DOC=bugfix
NO_TEST=covered by asan in #8901
NO_CHANGELOG=bugfix

The test has two groups, in front of each of which, a cluster is
created. Sometimes, it fails on the first test in every group:
either ro_reason is explicitly checked and it equals to `orphan`,
not nil, or we try to write to a still read-only instance and get
the error, that it's orphan.

The problem is the fact, that we don't wait until the connections
are established in a cluster. Let's add waiting for full mesh
in cluster creation.

Closes tarantool/tarantool-qa#320

NO_CHANGELOG=test fix
NO_DOC=test fix

Modify `actions/pack-and-deploy/action.yml` for creating static build
packages and deploying them to the repository via RWS service. Modify
`workflows/static_build_packaging.yml` for using this action.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Set variable `OUTPUT_DIR` in the .pack.mk file to the directory where
static build packages will be stored. This directory will be used for
the deployment.

Add target `deploy-static` for deploying deb and rpm packages via RWS.

NO_DOC=make
NO_TEST=make
NO_CHANGELOG=make

Update artifact paths in the static_build_packaging.yml workflow due to
fixing the issue with `OUTPUT_DIR` in the previous commit.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Before these changes, it was impossible to define a custom absolute
path for `OUTPUT_DIR` when calling the static-build/make_packages.sh
script. The build failed due to missing directory inside the container.
Also, set the default value for `OUTPUT_DIR` to the absolute path from
where the static-build/make_packages.sh script runs instead of relative
path to the static-build directory.

NO_DOC=build
NO_TEST=build
NO_CHANGELOG=build

Currently if tarantool exits during relay's final join stage,
corresponding thread isn't terminated. This causes the flakiness
of the replicaset_ro_mostly.test.lua.

Let's reuse the same relay, in which subscribe cord is running, for
the final join stage. This way the cord will be cancelled during
replication_free().

Closes #8082

NO_DOC=not user-visible
NO_TEST=fix flaky test
NO_CHANGELOG=not user-visible

Co-authored-by: Sergey Petrenko <sergepetrenko@tarantool.org>

The normalize_position() internal function is called by select/pairs to
prepare a position specified by the caller in the options.after argument
to be passed to C over FFI. The function encodes the position passed as
a table or a tuple in a temporary buffer obtained with cord_ibuf_take().
The problem is the cord buffer is already taken by the calling function
(select/pairs) to encode the search key. As a result, cord_ibuf_take()
allocates a new temporary buffer with malloc.

Let's avoid this extra buffer allocation by passing the taken buffer to
normalize_position(). Let's also remove the out arguments because they
are always set to iterator_pos and iterator_pos_end and instead set
iterator_pos and iterator_pos_end directly. To make this behavior clear,
we rename normalize_position() to iterator_pos_set(). We also remove
box.error() from this function and instead make it return true/false so
that the caller can release the buffer on failure.

perf/lua/box_select.lua test results:

                      base          patched
              get_0    159      153 (-  3%)
              get_1    243      243 (+  0%)
           select_0    227      227 (+  0%)
           select_1    343      336 (-  2%)
           select_5   2323     2305 (-  0%)
          select_10   6832     6866 (+  0%)
     select_after_0    687      558 (- 18%)
     select_after_1    746      524 (- 29%)
     select_after_5   2917     2704 (-  7%)
    select_after_10   5033     4979 (-  1%)
 select_fetch_pos_0    239      233 (-  2%)
 select_fetch_pos_1    418      413 (-  1%)
 select_fetch_pos_5   2492     2496 (+  0%)
select_fetch_pos_10   5121     5179 (+  1%)
            pairs_0    320      314 (-  1%)
            pairs_1   1060     1054 (-  0%)
            pairs_5   1466     1459 (-  0%)
           pairs_10   3749     3913 (+  4%)
      pairs_after_0    788      670 (- 14%)
      pairs_after_1   1813     1611 (- 11%)
      pairs_after_5   2764     2638 (-  4%)
     pairs_after_10   4150     4098 (-  1%)
          tuple_pos    116      117 (+  0%)

NO_DOC=perf improvement
NO_TEST=perf improvement

The test runs get, select, pairs space methods with various arguments in
a loop and prints the average method run time in nanoseconds (lower is
better).

Usage:

  tarantool box_select.lua

Output format:

  <test-case> <run-time>

Example:

  $ tarantool box_select.lua --pattern 'get|select_%d$'
  get_0 155
  get_1 240
  select_0 223
  select_1 335
  select_5 2321

Options:

  --pattern <string>  run only tests matching the pattern; use '|'
                      to specify more than one pattern, for example,
                      'get|select'
  --read_view         use a read view (EE only)

Apart from the test, this patch also adds a script that compares test
results:

  $ tarantool box_select.lua --pattern get > base
  $ tarantool box_select.lua --pattern get > patched1
  $ tarantool box_select.lua --pattern get > patched2
  $ tarantool compare.lua base patched1 patched2
         base          patched1          patched2
  get_0   149       303 (+103%)       147 (-  1%)
  get_1   239       418 (+ 74%)       238 (-  0%)

NO_DOC=perf test
NO_TEST=perf test
NO_CHANGELOG=perf test

This improves diff hunk name detection. Needed for checkpatch to
correctly detect if patched code belongs to a function.

NO_DOC=git
NO_TEST=git
NO_CHANGELOG=git

This patch introduces all flightrec options.

Part of #8861

NO_DOC=Was already described before.

Part of #8861

NO_DOC=Was already described before.

This patch fixes an issue in generate_column_metadata(). Prior to this
patch, the number of variable-only expressions was counted incorrectly
when temporary memory was allocated on region to store their positions.
However, although this allocation was incorrect, this did not lead to
any problems due to the specifics of the region allocations.

This patch fixes this by removing the temporary memory allocation.

Closes #8763

NO_DOC=no user-visible changes
NO_TEST=no user-visible changes
NO_CHANGELOG=no user-visible changes

It is possible for interval to have days, hours, minutes and seconds
larger than INT_MAX (or less than INT_MIN). Before this patch, msgpack
decoding had failed to parse intervals with msgpack int64 and uint64.
int64_t should be enough to store any value allowed for datetime
intervals.

Closes #8887

NO_DOC=small bug fix

Part of #8861

NO_DOC=Was already described before.

This patch introduces all feedback options.

Part of #8861

NO_DOC=Was already described before.

`api_check()` is the LuaJIT internal assertion. To prevent inconsistency
during internal assertion changes (for example, during backporting), use
glibc's `assert()` instead.

NO_DOC=internal
NO_TEST=internal
NO_CHANGELOG=internal

* FFI: Fix recording of union initialization.
* Fix maxslots when recording BC_VARG, part 2.
* Fix maxslots when recording BC_VARG.
* Fix BC_UCLO insertion for returns.
* ci: update job concurrency group definition

Part of #8825

NO_DOC=LuaJIT submodule bump
NO_TEST=LuaJIT submodule bump

A few options were added into box.cfg during development of the
declarative configuration module. As result the instance config schema
misses them. We're going to add these new options in #8861.

However, it would be nice to catch such situations automatically. The
new test case verifies it.

If a new box.cfg() option will be added or a default value of an
existing option will be changed, the test case will highlight it to let
a human decide what to do with the declarative config.

Part of #8861

NO_DOC=testing change
NO_CHANGELOG=see NO_DOC

box.cfg.vinyl_write_threads is 4 by default. Let's set the same value in
the declarative config as the default.

It seems, it was set to 2 by mistake.

Part of #8861

NO_DOC=bugfix
NO_CHANGELOG=the option is introduced after 3.0.0-alpha1 and there were
             no (pre)releases after that

Before this patch, one couldn't create new datetime interval with
boundary value from Lua. At the same time, it was possible to create
such interval from Lua through addition and subtraction. C range
verification allow to create boundary value intervals, error message
also implies that they should be allowed. (See #8878 for more info.)

Closes #8878

NO_DOC=small bug fix

This fixes gh_8613_new_cli_behaviour_test run with my custom .inputrc
(I use vi-cmd-mode-string/vi-ins-mode-string).

We already reset readline configuration in interactive_tarantool.lua.

Follows up ground works done for #7774

NO_DOC=test harness
NO_TEST=test harness
NO_CHANGELOG=test harness

To achieve that, we bypass the read-only check for the _truncate system
space in box_process1() and perform it in the on_replace system trigger
instead, when we know which space is truncated.

Note, we have to move the check for insertion of a new record into the
_truncate system space before the read-only check in the on_replace
trigger callback; this is needed for initial recovery with a non-empty
_truncate space to work. While we are at it, let's use recovery_state to
make the check explicit.

Closes #5616

@TarantoolBot document
Title: Mention that temp and local spaces can be truncated in ro mode

DML operations on temporary and local spaces can be performed even if
the instance is in the read-only mode, but DDL operations (such as
`alter`) are forbidden in this case[^1]. Technically, `truncate` is
a DDL operation so initially it was forbidden as well. However, it
should be safe to perform this operation on a temporary or local space
because logically it only modifies the data stored in the space (like
DML) and it isn't replicated (see tarantool/tarantool#4263). So starting
from Tarantool 2.11.1 we allow users to truncate temporary spaces in the
read-only mode.

[^1]: https://www.tarantool.io/en/doc/latest/concepts/replication/repl_architecture/#replication-local

A read source iterator stores statements in a vy_history object using
vy_history_append_stmt(). If a statement can be referenced, it's
reference counter is incremented. If it can't, i.e. it belongs to a
memory source, it's stored in a vy_history object without referencing.

This works fine because memory sources are append-only. A problem arises
only when we get to scanning disk sources. Since we yield while reading
disk, a dump task may complete concurrently dropping the memory sources
and possibly invalidating statements stored in the iterator history.
Although we drop the history accumulated so far and restart the
iteration from scratch in this case, there's still an issue that can
result in a use-after-free bug in vy_read_iterator_next().

The problem is that we access the current candidate for the next
statement while evaluating a disk source after a disk read. If 'next'
refers to a referenced statement, it's fine, but if it refers to a
statement from a memory source, it may cause use-after-free because
the memory source may be dropped during a disk read.

To fix this issue, let's make vy_history_append_stmt() copy statements
coming from memory sources. This should be fine performance-wise because
we copied memory statements eventually in vy_history_apply() anyway,
before returning them to the user.

Note that we also have to update vy_read_iterator_restore_mem() because
it implicitly relied on the fact that 'next' coming from a memory source
can't be freed by vy_mem_iterator_restore(), which cleans up the memory
source history. Now, it isn't true anymore so we have to temporarily
take a reference to 'next' explicitly.

Closes #8852

NO_DOC=bug fix
NO_TEST=tested by ASAN