Before this fix if requesting RPC by an invalid bucket_id we would send
an RPC to every replicaset to check if they have such a bucket_id.
This is not needed because we know the allowed range.

this adr is a proposal of implementing TRUNCATE sql command, its context and possible problems

- added the ability to build a base image manually

Виталий Шунков authored 3 months ago and Dmitry Rodionov committed 3 months ago

- combined the base image of picodata and sbroad
- refactor CI rules
- add RUST_VERSION and TARANTOOL_VERSION as variables in CI

Maksim Kaitmazian authored 3 months ago and Maksim Kaitmazian committed 3 months ago

This test is flaky due to vhsard rebalancing, so migrating to global
tables resolves the issue, since we don't use vshard for them. However,
after this migration one of the `pytest.raises` blocks's been failed,
as turned out, because u64::max value cannot be inserted in global tables.
We decided to don't fix this problem in this commit, so this check
was removed from the test and a new issue was added.

New issue: #1216

It fails a lot in CI lately. There are several open tickets:

#779
#1204

test: back to large (default) timeout in test_gitlab_763_no_missing_buckets_after_proc_sharding_failure

Close: #1032