ydb - Mirror of YDB github repos

	Commit message (Collapse)	Author	Age	Files	Lines
*	Unpoison use-after-dtor access to ref counter	makxenov	9 days	1	-1/+1
\| \| \| \| \| \| \| \|	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
*	Replace DangerousGetPtr with TWeakPtr	babenko	2026-03-01	1	-7/+29
\| \| \| \|	commit_hash:866e4401ff3564ae6e58c067f937c15d322a3828
*	YT-27536: Fix (seemingly benign) race in TTwoLevelFairShareQueue	babenko	2026-02-28	1	-226/+49
\| \| \| \|	commit_hash:700b15a49621e9f79e6e6c725a1aa958f9bd132e
*	Do not get ref counter when copy weak ptr	thenewone	2025-09-25	1	-2/+7
\| \| \| \| \| \| \| \| \| \| \|	Если копировать TWeakPtr в момент разрушения объекта, на который он ссылается, то происходит гонка на vptr. GetRefCounter использует vptr, а деструктор объекта может его менять. Thread-sanitizer эту гонку видит. Unit test added; also fixed and enabled older test. Enabled thread sanitizer for library/cpp/yt/memory. commit_hash:87cb083a9905cc8a262b575868bbae3438b9324f
*	add ::element_type, .get() to smart pointers for better compatibility with std	pavook	2024-11-04	1	-0/+1
\| \| \| \| \|	For example, this makes it possible to use gtest pointer matchers on smart pointers commit_hash:2650074ae18ee35696b297d3d1f0393e7350789f
*	Library import 8 (#1074)	AlexSm	2024-01-18	1	-3/+3
\| \| \| \| \|	* Library import 8 * Add contrib/libs/cxxsupp/libcxx/include/__verbose_abort
*	Removed the last typedefs in the codebase	sabdenovch	2023-08-28	1	-1/+1
\| \| \| \| \|	removed a lot of typedefs and turned a couple of std::pairs into something more meaningful
*	Intermediate changes	robot-piglet	2023-06-30	1	-15/+33
\|
*	Fix typos in library/cpp/yt	babenko	2023-06-03	1	-1/+1
\|
*	Intermediate changes	robot-piglet	2023-03-21	1	-1/+2
\|
*	Restoring authorship annotation for <[email protected]>. Commit 2 of 2.	klyachin	2022-02-10	1	-2/+2
\|
*	Restoring authorship annotation for <[email protected]>. Commit 1 of 2.	klyachin	2022-02-10	1	-2/+2
\|
*	Restoring authorship annotation for <[email protected]>. Commit 2 of 2.	psushin	2022-02-10	1	-7/+7
\|
*	Restoring authorship annotation for <[email protected]>. Commit 1 of 2.	psushin	2022-02-10	1	-7/+7
\|
*	Restoring authorship annotation for <[email protected]>. Commit 2 of 2.	babenko	2022-02-10	1	-40/+40
\|
*	Restoring authorship annotation for <[email protected]>. Commit 1 of 2.	babenko	2022-02-10	1	-40/+40
\|
*	Restoring authorship annotation for <[email protected]>. Commit 2 of 2.	ignat	2022-02-10	1	-1/+1
\|
*	Restoring authorship annotation for <[email protected]>. Commit 1 of 2.	ignat	2022-02-10	1	-1/+1
\|
*	Restoring authorship annotation for <[email protected]>. Commit 2 of 2.	lukyan	2022-02-10	1	-92/+92
\|
*	Restoring authorship annotation for <[email protected]>. Commit 1 of 2.	lukyan	2022-02-10	1	-92/+92
\|
*	Restoring authorship annotation for <[email protected]>. Commit 2 of 2.	max42	2022-02-10	1	-19/+19
\|
*	Restoring authorship annotation for <[email protected]>. Commit 1 of 2.	max42	2022-02-10	1	-19/+19
\|
*	Restoring authorship annotation for <[email protected]>. Commit 2 of 2.	prime	2022-02-10	1	-11/+11
\|
*	Restoring authorship annotation for <[email protected]>. Commit 1 of 2.	prime	2022-02-10	1	-11/+11
\|
*	intermediate changes	Devtools Arcadia	2022-02-07	1	-0/+314
	ref:cde9a383711a11544ce7e107a78147fb96cc4029