The `log_level' configuration parameter can be set as a number or a string.
When it is a string, cfg_geti() returns 0. Use log_default->level instead,
which is initialized earlier during box_init_say().

Closes #8287

NO_DOC=bugfix
NO_CHANGELOG=minor bug

(cherry picked from commit 41ead021)

This patch fixes an assertion or segmentation error if a FOREIGN KEY or
CHECK constraint is declared before the first column.

Closes #8392

NO_DOC=bugfix of the bug added in the current release
NO_CHANGELOG=bugfix of the bug added in the current release

We use coio_connect() to connect the replica to a remote peer. It
implies no timeout, and does a non-blocking connect() to the peer and
then waits for the socket to become writable indefinitely.

When the remote peer changes its IP address, connect() might try
connecting to the old address for as long as ~ 2 minutes (given the
default tcp_syn_retries value of 6).

This blocks replica from trying to reconnect to the updated address and
is pretty inconvenient.

Let's use coio_connect_timeout() instead and use
replication_disconnect_timeout() as a timeout, like everywhere else in
master-replica communication.

Closes #7294

NO_DOC=bugfix

(cherry picked from commit 0486a489)

Add missing `server:drop()` to digest_crc32_recording_test.lua to avoid
running tarantool processes after the test.

NO_DOC=test fix
NO_TEST=test fix
NO_CHANGELOG=test fix

(cherry picked from commit 5cbb0daf)

The test fails with

 fail | 2023-03-01 15:54:30.550 [3724975] main/103/server_instance.lua
 F> can't initialize storage: unlink, called on fd 63,
 aka unix/:(socket), peer of unix/:(socket): Address already in use

We fixed a similar issue in commit 3d3e9dea ("test: fix flaky
box-luatest/gh_7917_log_row_on_recovery_error_test") by using unique
instance names. Let's do the same here.

Fixes commit b1095c1c ("memtx: fix force recovery handling").
Follow-up #7974

NO_DOC=test
NO_CHANGELOG=test

(cherry picked from commit 1490228a)

Force recovery needs to follow the following logic: any unsuccessful system
space request must make recovery fail (including failure to decode an xrow,
when we are not sure we have finished processing system space request). If
the request is a non-insert one (e.g., raft or synchro) or addresses a user
space, it means we have finished processing system space requests, and from
this moment force recovery can be enabled — change the behaviour
accordingly.

We assume the request order in the snapshot is the following:
1. system space requests;
2. user space requests;
3. non-insert requests (e.g., raft or synchro).

Refactor the force recovery logic: add a enumeration to track snapshot
recovery state and add a new diagnostic for the case when the snapshot
contains has no system spaces.

Closes #7974

NO_DOC=bugfix

(cherry picked from commit b1095c1c)

In some cases we don't have the whole space struct, but we want to
determine whether the provided space identifier corresponds to a system
space — add a `space_id_is_system` helper and refactor `space_is_system` to
reuse it.

Needed for #7974

NO_CHANGELOG=refactoring
NO_DOC=refactoring
NO_TEST=refactoring

(cherry picked from commit 928e5733)

We often commit snap/xlog files for tests. A snap/xlog file is binary,
but it contains a plain text header and, as a result, may be identified
as a text file by git, which would enable checkpatch checks for it.
Apparently, we don't need to check these files so let's force git to
identify them as binary.

NO_DOC=git
NO_TEST=git
NO_CHANGELOG=git

(cherry picked from commit 24dd505f)

Follows up #8363

NO_CHANGELOG=see previous commit
NO_DOC=added a test

(cherry picked from commit cccd1f9a)

Patch fixes a bug when body in response couldn't be decoded:

NO_WRAP
```
tarantool> httpc = require('http.client').new()
tarantool> response = httpc:get('https://jsonplaceholder.typicode.com/todos/1'

)
tarantool> response:decode()

---
- error: 'builtin/http.client.lua:301: attempt to index field ''decoders'' (a nil
    value)'
...
```
NO_WRAP

Now response object contains table with decoders defined by user in his
http client instance. We hide this table on response serialization by
adding underscore because decoders there is not a part of API.

Reported-by: Alexander Turenko <alexander.turenko@tarantool.org>

Fixes #8363

NO_DOC=bugfix

(cherry picked from commit 83168b25)

* test: make skipcond helper more convenient
* test: introduce test:skiprest TAP helper
* test: introduce test:skipall TAP helper
* test: stop using utils.selfrun in tests
* ci: use LuaJIT-test target in testing workflows

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

This commit adds the RFC for the sysprof that
was approved a year ago.

Part of #781

NO_DOC=RFC
NO_TEST=RFC
NO_CHANGELOG=RFC

(cherry picked from commit 958a1503)

Updating libcurl from 7.84.0 to 7.87.0 in commit 09f4eca1
("third_party: update libcurl from 7.84.0 to 7.87.0")
made it impossible to built tarantool with bundled curl with nghttp2,
because nghttp2 was not updated to fit libcurl 7.87.0, this led to
missing function
nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation
during linking step.

https://github.com/nghttp2/nghttp2/releases/tag/v1.52.0

Closes #8268

NO_DOC=there is no known behavior changes, consider the change as not
       visible for a user
NO_TEST=can only reproduce in specific environment
NO_CHANGELOG=see NO_DOC

(cherry picked from commit a6fae421)

Error labes got mixed up. Fix the order and add a test.

Fixes commit 3f026339 ("vinyl: implement iterator pagination").

Closes #8372

NO_DOC=bug fix
NO_CHANGELOG=fix for unreleased feature

(cherry picked from commit 074e4eb8)

Remove released entries.

NO_DOC=minor
NO_TEST=minor
NO_CHANGELOG=minor

When calculating `rows_index` in `netbox_decode_execute` etc we use
implementation defined behavior of compiler. `i < mapsize` and this is
fine according to standard as unsigned arithmetic is well defined on
overflows. But then we cast the result to int and this is implementation
defined as the result can not be represented by int.

Closes https://github.com/tarantool/security/issues/98

NO_DOC=minor
NO_TEST=minor
NO_CHANGELOG=minor

(cherry picked from commit baba38e6)

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

Proofread changelogs for 2.11.0-rc, part 3
Fix grammar, punctuation, and wording

NO_CHANGELOG=changelog
NO_DOC=changelog
NO_TEST=changelog

There is no sense to add description of changes that will be present as
part of 2.10.5 into 2.11.0-rc1 release notes. Let's base the changes
list on current 2.10 (future 2.10.5).

Follows up commit 4d95d1e2 ("Cleanup released changelogs").

NO_DOC=no code changes, just changelogs
NO_TEST=see NO_DOC

In Tarantool EE the version string is "Tarantool Enterprise", not just
"Tarantool".

Fixes commit a984fc0d ("debugger: use option -d for debugger
activation")

NO_DOC=test
NO_CHANGELOG=test

The new compat option 'fiber_slice_default' is added to control
the default value of the max fiber slice. The old default is no limit
(both warning and error slice equals TIMEOUT_INFINITY). The new default
is {warn = 0.5, err = 1.0}.

Follow-up #6085

NO_DOC=tarantool/doc#3057
NO_CHANGELOG=unreleased

This commit adds the new field 'max_slice' to fiber.info() that reports
the max slice applied to the given fiber. The value is a table with two
fields: 'err' for error slice and 'warn' for warning slice. Values
greater than or equal to TIMEOUT_INFINITY aren't reported.

Follow-up #6085

NO_DOC=tarantool/doc#3057
NO_CHANGELOG=unreleased

Error messages raised when an invalid slice is specified are confusing:

  tarantool> fiber = require('fiber')
  ---
  ...

  tarantool> fiber.set_max_slice('foo')
  ---
  - error: slice must be a table or a number
  ...

  tarantool> fiber.set_max_slice({})
  ---
  - error: 'bad argument #3 to ''?'' (number expected, got nil)'
  ...

Let's change the error message to "slice must be a number or a table
{warn = <number>, err = <number>}".

Follow-up #6085

NO_DOC=undocumented
NO_CHANGELOG=unreleased

One may encode a non-printable string under the MsgPack type MP_STR.
In fact, there's no way to encode binary data as MP_BIN from Lua so
users often do that, which breaks our gdb extension. Let's encode a
string in base64 if unicode() raises an error, like we do with MP_BIN.

While we are at it,
 - escape double quotes in printable strings;
 - fix MP_BIN encoding (b64encode takes and returns bytes).
 - don't use YAML !!binary prefix before base64 data - use bin: and str:
   instead.

Here's what it looks like:

```
(gdb) p *box_tuple_last
  <...>
  data = ["\"тест\\foo\"", str:/w==, bin:/w==]}
```

The tuple was created with the following command:

```
tarantool> msgpack = require('msgpack')
---
...

tarantool> box.tuple.new(
         >   msgpack.object_from_raw('\xae"тест\\foo"'), -- MP_STR unicode
         >   msgpack.object_from_raw('\xa1\xff'),        -- MP_STR binary
         >   msgpack.object_from_raw('\xc4\x01\xff'))    -- MP_BIN
---
- ['"тест\foo"', !!binary /w==, !!binary /w==]
...
```

Follow-up commit 08a171a4 ("gdb: support unicode in MP_STR type of
MsgPack").

NO_DOC=gdb extension
NO_TEST=gdb extension
NO_CHANGELOG=gdb extension

It doesn't belong to Tarantool sources. The tools directory looks like
the right place for it.

NO_DOC=code cleanup
NO_TEST=code cleanup
NO_CHANGELOG=code cleanup

This patch allows to downgrade tuple foreign keys to SQL foreign keys
and some tuple check constraints to SQL check constraints. The only
tuple check constraints that can be downgraded are those using functions
with the SQL_EXPR language.

Closes #7718

NO_DOC=already introduced
NO_CHANGELOG=already introduced

Added `-d` option for activation of debugger shell:
- it calls debugger shell in `luadebug.lua` instead of
  a standard interactive shell from `console.lua`;
- that option complements original way for starting a
  debugging shell via `require 'luadebug'()`, but is a
  little bit easier.

NB! At the moment when we enter debugging mode instead of
a standard Tarantool console, we change banner to:
```
Tarantool debugger 2.11.0-entrypoint-852-g9e6ed28ae
type 'help' for interactive help
```

Part of #7456

@TarantoolBot document
Title: Command-line option `-d` for console debugger.

Please see third_party/lua/README-luadebug.md for a full description
of different ways to activate debugging shell.

* ci: add LUAJIT_ENABLE_CHECKHOOK for exotic matrix
* ci: add ARM64 architecture to exotic testing
* ci: update action/checkout to v3
* Fix os.date() for wider libc strftime() compatibility.
* x86/x64: Fix loop realignment.
* ci: introduce workflow for exotic builds
* sysprof: fix interval parsing in dual-number mode
* test: add test for `string.format('%c', 0)`
* ci: drop obsolete arguments for LuaJIT integration

Part of #8069

NO_DOC=LuaJIT submodule bump
NO_TEST=LuaJIT submodule bump

2.10.5 version is going to be released at the same time as 2.11.0 thus
let's add it to the box.schema.downgrade_versions().

NO_DOC=internal
NO_CHANGELOG=internal
NO_TEST=internal

Currently it's possible to set the log level for a particular Lua module,
or to change the default log level, however there is no way to change it
only for Tarantool system messages. This patch introduces a fake module
name "tarantool" for this purpose.

Closes #8320

NO_CHANGELOG=Unreleased feature
NO_DOC=Will update tarantool/doc#3264

We used to "normalize" breakpoint filename paths
down to their basic name, which worked fine for
unique file names, but is getting annoying when
you need to debug a code in one of many `init.lua`
modules, i.e.

    break init.lua:5

Will stop at _every_ `init.lua` file we will run
at the debugging session.

So we add machinery for partial paths lookup, to
make possible to set breakpoints using (unique-enough)
path suffixes, e.g. if we have multiple `init.lua` in
the application, i.e.
    ./init.lua
    ./A/init.lua
    ./B/init.lua

Then we could use syntax:

    break A/init.lua:5

To activate debugger breakpoint only in the particular
module, and not trigger it elsewhere.

Current suffix trees limitations and peculiarities
--------------------------------------------------

Please keep in mind that suffix-tree algorithm, used for
partial paths lookup, uses `$ref` and `$f` node names
for their own purposes. That means that it would not handle
well breakpoints with paths containing `$f` and `$ref`.
That's not a big problem given that majority of filesystems
we are running on do not usually allow `$` as part of
file name.

Also, due to suffix tree lookup behavior, if we would
activate multiple breakpoints:
    break init.lua:10
    break A/init.lua:10

Then _least specific_ `init.lua:10` breakpoint will trigger.
From users' prospective it makes no much difference, as we
need to stop in debugger shell in this line, but this is
the way how suffix tree is working.

Dot files treatment
-------------------

There is a special mechanism for `.` and `..` treatment
if they are at the header of a path provided. I.e.

    break ./main.lua:10
    break ../a/b/c/least.lua:15

For these cases `.` and `..` will be converted to the
full path to the given file location.

NO_TEST=hard to implement tests. Postponed till step.5

@TarantoolBot document
Title: Breakpoints in console debugger for Lua

Match partial path patterns in breakpoints
==========================================

Please see `third_party/lua/README-luadebug.md` for
a fuller description of partial path syntax one could use
in a breakpoints definition.

We used to "normalize" breakpoint filename paths
down to their basic name, which worked fine for
unique file names, but is getting annoying when
you need to debug a code in one of many `init.lua`
modules, i.e.

    break init.lua:5

Will stop at _every_ `init.lua` file we will run
at the debugging session.

So we add machinery for partial paths lookup, to
make possible to set breakpoints using (unique-enough)
path suffixes, e.g. if we have multiple `init.lua` in
the application, i.e.
    ./init.lua
    ./A/init.lua
    ./B/init.lua

Then we could use syntax:

    break A/init.lua:5

To activate debugger breakpoint only in the particular
module, and not trigger it elsewhere.

NB! If we will activate multiple breakpoints:
    break init.lua:10
    break A/init.lua:10

Then _least specific_ `init.lua:10` breakpoint will trigger.
From users' prospective it makes no much difference, as we
need to stop in debugger shell in this line, but this is
the way how suffix tree is working.

NO_TEST=hard to implement tests. Postponed till step.5

@TarantoolBot document
Title: Breakpoints in console debugger for Lua

Match partial path patterns in breakpoints
==========================================

Please see `third_party/lua/README-luadebug.md` for
a fuller description of partial path syntax one could use
in a breakpoints definition.

* Added breakpoints support in debugger;

NO_TEST=documentation added

@TarantoolBot document
Title: Breakpoints in console debugger for Lua

Breakpoints support
===================

Please see `third_party/lua/README-luadebug.md` for
a description of breakpoints support introduced to the
builtin console debugger in `luadebug.lua`.

Commonize mechanism activated by `dbg.cfg.auto_where` and an
automatic code listing we show for breakpoint context.

Make sure we do not show redundant listing, i.e. after
commands `where #`, or `up`, or `down` we do not output
automatic listing, as there was already shown some different
context.

NO_DOC=see later
NO_CHANGELOG=internal
NO_TEST=internal

Make message, which is shown for a `help` command,
to be more readable.

NO_DOC=see later commit
NO_CHANGELOG=internal
NO_TEST=internal

Introduced `dbg_write_error` to centralize the way
how errors reported in debugger shell.

Similarly `dbg_write_warn` is used for reporting of
highlighted non-fatal warnings.

NO_DOC=internal
NO_CHANGELOG=internal

We may use "caret" or "arrow" symbols either in
colored or uncolored contexts. To reduce further
confusion we get rid of colored prefixes.

NO_DOC=internal
NO_CHANGELOG=internal
NO_TEST=internal

In many cases we do not need to use all "Snl"
parameters in `debug.getinfo()`: so try to trim wherever
possible "n", which is calculating `name` and `namewhat`,
and "S" which is generating `source`, `short_src` and others.

NO_DOC=internal
NO_CHANGELOG=internal
NO_TEST=internal

Visualize properly locations with breakpoints
saved there. In addition to current line visualization
(using green '=>') we annotate corresponding line with
red "●".

NO_TEST=see the later commit
NO_DOC=internals
NO_CHANGELOG=internals

Introduced few new commands to handle breakpoints:
- `b file:NNN` to set new breakpoint;
- `bd file:NNN` to remove breakpoint;
- 'bl` to list all active breakpoints.

There is partial breakpoint notation supported when
for `b :N` or `b +N` breakpoint will be set to the
asked line in the _currently_ debugged file.

Changed `c` (continue) to stop on breakpoints, if there any active
one asssigned by user. Otherwise it still run in full speed, without
any hook check.

NO_DOC=see the later commit
NO_CHANGELOG=see the later commit