Антон Фетисов authored 1 month ago and Егор Ивков committed 1 day ago

This allows to easily print the whole underlying error chain by traversing errors via
Error::source method, instead of effectively erasing underlying errors as it currently happens.
Note that `thiserror`, unlike `anyhow`, doesn't provide a way out of the box to print the error
chains. Some other library or custom code need to be written to get all errors. However, this
commit makes better error printing a purely local decision.

This commit doesn't change any printing of errors via default Display or Debug impls, not does it
change the layout of error types.

Dmitry Rodionov authored 4 days ago and Maksim Kaitmazian committed 4 days ago

Do not expect one ticket with matching name as other tickets may contain
test id in its body. So instead of asserting on one issue in the result
set go through entire search result to pick issue with the matching
title

Erik Khamitov authored 1 week ago and Maksim Kaitmazian committed 6 days ago

- Fixed incorrect parameter handling in get_expression_node() by converting Node::Parameter to Expression::Parameter.
- Corrected Group By parameter handling by moving the replacement of group-by ordinals with references before plan caching.

The test 'test_mtls_with_known_cert' was failing due to expired SSL certificates.
The certificate has expired a few days ago, so it's failing with error - 'SSL error: ssl/tls alert certificate expired'.
This update replaces the expired certificates with new ones, ensuring that the tests pass.
The new certificates are valid for the next 180 years.

Speed up test_cli_ux.py::test_do_not_ban_admin_via_unix_socket.
Removed check for aliveness of instance after fail of sql query
with auth error, so we don't wait 1 second in wait child.

It is not useful for us, but sometimes creates problems when poetry
tries to access sytem keyring to download packages in certain
environments (WSL)

Close #1297

We should also update tarantool's crash handler to print picodata
version in there, but this requires patching tarantool.

when executing TRUNCATE

The reason of flaky is a well known bucket rebalancing during SQL
query execution. One day we'll fix our vshard issues, but not today.
So, lets switch to a single instance test cluster.

`FOR ALL TIERS` semantic now is default.

For example, `ALTER SYSTEM SET parameter TO 1`
is equal `ALTER SYSTEM SET parameter TO 1 FOR ALL TIERS`
for parameters with scope tier.