Mirror of YDB github repos https://code.mastervirt.ru/ydb/atom?h=22.2.22 2022-04-18T21:12:03Z 2022-04-18T21:12:03Z alexnick alexnick@yandex-team.ru 2022-04-18T15:53:14Z urn:sha1:92cbd3386a007ad2ae0f3456db799df7d1dc7ea4 fix relations REVIEW: 2455896 REVIEW: 2457133 x-ydb-stable-ref: 5123070da3815c351de94b3400369e17d105b4bd 2022-04-18T18:02:25Z Alexey Borzenkov snaury@yandex-team.ru 2022-04-18T15:53:13Z urn:sha1:8ac7e099cde33754904185e97adf87d2d6bf9ef7 Merge from trunk: r9334121 REVIEW: 2454367 x-ydb-stable-ref: b6eb47536c42075f0f6c9a23f9835351edb9e83d 2022-04-18T18:02:25Z alexnick alexnick@yandex-team.ru 2022-04-18T15:53:13Z urn:sha1:ca2df771961af490d9e71d59148a40f8b03e7446 correct error codes Note: mandatory check (NEED_CHECK) was skipped REVIEW: 2453925 x-ydb-stable-ref: 19728da96711de9e81de9ef2cf8067357c4f09b5 2022-04-18T18:02:24Z alexnick alexnick@yandex-team.ru 2022-04-18T15:51:22Z urn:sha1:556795dc3e07c5497b7537aeadc7a17183b3aa51 switch metrics registry to shared_ptr KIKIMR-14218 REVIEW: 2369561 support of http kinesis proxy inside ydb KIKIMR-14665 REVIEW: 2445707 LOGBROKER-7369 Add TCP_USER_TIMEOUT option on client socket Unfortunately timeout issue can only be reproduced in special conditions: - tests are run locally - the order of tests is as follows: GoodRequestGetRecords and GoodRequestGetRecordsLongStreamName should be executed one after another. In debugger one can clearly see the infinite waiting in socket. Thereby the TCP_USER_TIMEOUT option fixes it. Moving GoodRequestGetRecordsLongStreamName up or to a different TEST_SUITE fix the issue as well though. REVIEW: 2433681 LOGBROKER-7298 Fix verify on GetRecords call Fix VERIFY issue REVIEW: 2406664 LOGBROKER-7373 Fix empty body in error response Fix empty body in error responce from http proxy REVIEW: 2396287 LOGBROKER-7369 Fix local run of http proxy tests Fix local run of http proxy tests Actor HTTP server listens on IPv6 localhost, e.g. [::] Tests send data to localhost. Resolving of localhost works differently from system to system. Replace localhost to 127.0.0.1 or :: depending on use case. REVIEW: 2393055 REVIEW: 2451066 x-ydb-stable-ref: 22bc438d32d05e166c59a3e0e4afb51da8103c3a 2022-04-18T15:40:43Z Vitalii Gridnev gridnevvvit@gmail.com 2022-04-18T15:40:43Z urn:sha1:36b7a2ccb885e2d29b7f23380d6cc6c8aae8a3d7 REVIEW: 2449087 REVIEW: 2453741 x-ydb-stable-ref: d75b8a63a96d690695b263fbf446189f2751d30a 2022-04-18T15:40:42Z Alexey Borzenkov snaury@yandex-team.ru 2022-04-18T15:40:42Z urn:sha1:371f1310741470aa1d5fb05c218178926cfb927f Merge from trunk: r9329733 REVIEW: 2452031 x-ydb-stable-ref: 1c6954d8b25f3c623cda07eeeacd0b33e101b201 2022-04-18T15:40:42Z Ilnaz Nizametdinov i.nizametdinov@gmail.com 2022-04-18T15:40:42Z urn:sha1:0ac452f25c833389cde78dfebf3ecc3a591a3c14 merge from trunk: r9327124 REVIEW: 2449821 x-ydb-stable-ref: 3e721c31fcf405448900453bbcab2fb74a692320 2022-04-18T15:40:40Z alexnick alexnick@yandex-team.ru 2022-04-18T15:40:40Z urn:sha1:71cda950d3a57162ee7578d3c87b29709c95107e fix for empty messages Note: mandatory check (NEED_CHECK) was skipped fix for YQ-1022 Note: mandatory check (NEED_CHECK) was skipped REVIEW: 2449884 x-ydb-stable-ref: e06cc260218d5d5123ea909d512ad31f003eba3f 2022-04-18T15:40:40Z svc svc@yandex-team.ru 2022-04-18T15:40:40Z urn:sha1:f36b0de500d375e077505db23c806891ff05a21f REVIEW: 2448468 REVIEW: 2449553 x-ydb-stable-ref: 3b70ae0924f3d19b5d160fe85ab4f1045525aaaf 2022-04-18T15:40:39Z Alexey Borzenkov snaury@yandex-team.ru 2022-04-18T15:40:39Z urn:sha1:d76a9719a8a0f4da477dc6972187e24550d4b706 REVIEW: 2444057 x-ydb-stable-ref: 27ed40f9a68a102d24254ad6aed5f6b74bddccb2