Commits
- Commit:
4f3d3726fd95fea6a253b68332d39491479a5b65
- From:
- Sergey Bronnikov <sergeyb@tarantool.org>
- Date:
test/static: add a seed corpus for decimal_to_int64_fuzzer
NO_DOC=seed corpus
NO_CHANGELOG=seed corpus
NO_TEST=seed corpus
- Commit:
cbf7749b2fd71caa8504a2bed0225072403f41fe
- From:
- Sergey Bronnikov <sergeyb@tarantool.org>
- Date:
test/fuzz: add fuzzing test for decoding decimals
NO_DOC=testing
NO_CHANGELOG=testing
- Commit:
9706f42d3dbb25dda255cd5092df3a41a8053ace
- From:
- Sergey Bronnikov <sergeyb@tarantool.org>
- Date:
test/static: add a seed corpus for IPROTO decoders
NO_DOC=seed corpus
NO_CHANGELOG=seed corpus
NO_TEST=seed corpus
- Commit:
187a2bf9abeb4a11e1e8a28ca012242e8776eb99
- From:
- Sergey Bronnikov <sergeyb@tarantool.org>
- Date:
test/fuzz: add fuzzing tests for IPROTO decoders
Examples of IPROTO decoding issues: #3900, #1928, #6781.
Patch adds a number of fuzzing tests that covers IPROTO decoding:
- xrow_decode_auth
- xrow_decode_begin
- xrow_decode_call
- xrow_decode_dml
- xrow_decode_error
- xrow_decode_id
- xrow_decode_raft
- xrow_decode_sql
- xrow_decode_watch
- xrow_greeting_decode
- xrow_header_decode
NO_DOC=testing
NO_CHANGELOG=testing
- Commit:
0cb91010c2a52e1ff3d7d6d467a71e7117778413
- From:
- Alexander Turenko <alexander.turenko@tarantool.org>
- Via:
- Alexander Turenko <totktonada.ru@gmail.com>
- Date:
config: allow to call config:get() from app script
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