ydb/library, branch mainMirror of YDB github reposhttps://code.mastervirt.ru/ydb/atom?h=main2026-07-22T01:05:02ZSync branches 260722-01012026-07-22T01:05:02ZYDBotydbot@ydb.tech2026-07-22T01:05:02Zurn:sha1:1ac975d35cdfff725e931e259da2fe48add1b5f7add methods ForEach() and ForEachReverse() to TPagedVector for fast iteration over elements2026-07-21T15:07:53Ztobotobo@yandex-team.com2026-07-21T14:03:46Zurn:sha1:7c315681e7b727ddfbcff15e438d2fb040996d28
commit_hash:3cde1a78c5f1af49a50168bbc85c6f9a8f28ad73
Make THROW_ERROR_EXCEPTION_UNLESS/IF chainable with error attributes2026-07-21T06:52:42Zpechatnovpechatnov@yandex-team.com2026-07-21T06:21:36Zurn:sha1:b6bda2264da6775be09d9224c82c5b9587e60052
commit_hash:4e76ece0b75ab787ed04b6be5f183cecbf9b8167
Sync branches 260721-01012026-07-21T01:03:14ZYDBotydbot@ydb.tech2026-07-21T01:03:14Zurn:sha1:80af15dc73b12701f0b7b9302fb444becb777620fix fork deadlock2026-07-20T16:12:08Zmixx239mixx239@yandex-team.com2026-07-20T15:41:43Zurn:sha1:7a9820fea09300733ed584f4851707a5c5987689
Python-клиент (обертка над С\+\+ клиентом) UA с fork support виснет в `fork()` (\>50%): `TClientSession::CheckGrpcCallInactivity` (inactivity-watchdog на потоке gRPC completion-queue) брал сессионный лок `with_lock` не проверив что не идет форк. Пока pthread_atfork-обработчик `TClient::PreFork` держит этот лок в `WaitAll()`, поллер застревает на CheckGrpcCallInactivity -\> сессия не закрывается -\> `fork()` не завершается.
Фикс: `CheckGrpcCallInactivity` захватывает лок `TryAcquire` \+ выход по `ForkInProgress` - как уже делает `Poll()`
commit_hash:79b1f727d8ecc9b54e386b586f4f49bf1d6512d8
Sync branches 260718-01002026-07-18T01:03:09ZYDBotydbot@ydb.tech2026-07-18T01:03:09Zurn:sha1:6404eb0d40862428d6fa27fe83cc0e69531e371bIntermediate changes2026-07-17T22:14:29Zrobot-pigletrobot-piglet@yandex-team.com2026-07-17T21:00:24Zurn:sha1:022ba221745d5d7363e508cc1ba04bac51a62baf
commit_hash:7466cacb2971d86743b7541ddb2fbb6c8850085a
Make Ascii-related functions and StripString() constexpr2026-07-17T19:23:20Zthegeorgthegeorg@yandex-team.com2026-07-17T17:02:10Zurn:sha1:4a3634c81d134200825ad9db61bc73962b398fbd
commit_hash:ff7ca9a2428930638288f8c0e92a303b8f620063
move dqrun to yt/2026-07-17T16:17:43Zuzhasuzhas@yandex-team.com2026-07-17T13:30:05Zurn:sha1:09cd02b72802d18ce7257ba17ef8337e669be85c
- Move `contrib/ydb/library/yql/providers/dq/{config,local_gateway,service,stats_collector}` and gateway/control implementation to `yt/yql/providers/dq/`
- Move `contrib/ydb/library/yql/tools/dqrun` to `yt/yql/tools/dqrun`
- Clean up `contrib/ydb` provider (slim `yql_dq_gateway.h`, PEERDIR updates) and fix consumers (`scheduler`, `global_worker_manager`, `pq/provider/ut`, benchmarks, solomon tests)
## Test plan
- [x] `./ya make --build debug contrib/ydb/library/yql/providers/dq/provider contrib/ydb/library/yql/providers/dq/provider/exec yt/yql/providers/dq/gateway yt/yql/providers/dq/local_gateway yt/yql/providers/dq/service yt/yql/tools/dqrun`
- [x] `./ya make --build debug -tA yt/yql/providers/dq/provider/ut`
commit_hash:18a321f318f5903167749b88541a79b34ab1c8d7
Unpoison use-after-dtor access to ref counter2026-07-17T10:21:08Zmakxenovmakxenov@yandex-team.com2026-07-16T17:48:23Zurn:sha1:bcb14ace638c50d3f0530f65ce3e9ad1e7b3d361
Two scenarios addressed:
- Access to ref counters after explicit destructor of an object
- Access to vptr for upcast of an already destroyed object
commit_hash:a8f27500111817f325832d006feb3ce6c3c830f1