| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
From hash: [af01597c047856b865c6a4e9933cfeacb0a2f39b](https://a.yandex-team.ru/arcadia/commit/af01597c047856b865c6a4e9933cfeacb0a2f39b)
From revision: [14032879](https://a.yandex-team.ru/arcadia/commit/rXXXXXX)
[CI flow](https://a.yandex-team.ru/projects/ya_make/ci/releases/flow?dir=devtools%2Fya&id=release-ymake&version=191)
Flow triggered by user: [robot-ci](https://staff.yandex-team.ru/robot-ci)
Update tools: ymake, os_ymake
ac5a20d07f8777991019eed587bc65966d19fe51
|
|
|
|
|
|
|
|
|
|
|
|
| |
Мелкий фикс неверных исключений. Как будто у меня локально повторялось как минидамп на колонке (не отловленное исключение)
Зависит от реализации libc. Но кажется что исходный вариант все же не верный:
[ The value in errno is significant only when the return value of
the call indicated an error (i.e., -1 from most system calls; -1
or NULL from most library functions); a function that succeeds is
allowed to change errno. The value of errno is never set to zero
by any system call or library function.](https://man7.org/linux/man-pages/man3/errno.3.html)
1d2088da57c98f9d9abfd6da865219fcf74db212
|
|
|
|
| |
924b35169e93d0a6cf268fa4bd556a12e3477762
|
| |
|
|
|
|
| |
af83e035a87a6ca819fd272695041701f3639768
|
| |
|
| |
|
|
|
|
| |
2f47b5eab59c8031971bd995b703c854fd6f106d
|
|
|
|
| |
4738445240b36d24604dbf9955309608fc9568df
|
|
|
|
| |
520961d4315ab4738f60613278b7e63765341b85
|
|
|
|
| |
d7289b88c1b52abc27589ed0480714656864f213
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, there was a bug, when first element of an ACL would be evaluated (when not needed) if:
1. Said element had subject_tag_filter_specified;
2. User did not satisfy aforementioned filter.
Now there is a check for it.
Also added new timer metrics for CheckPermission and a panic button to disable attribute-based access control.
1a1d8d814a23e9a5000f2be3fe83c519947971b4
|
|
|
|
| |
1ee76574376bb2910f9e1b91f9b527b13bb392d3
|
|
|
|
| |
855bd01a1b384d08c59ee86c6b493ea32190ef19
|
|
|
|
| |
59379f119eb5f2fd036edea64923ff53b96c9028
|
|
|
|
| |
3a95ba7ea18b67eb6bd8d04631814456f4881138
|
|
|
|
| |
a89e46aed68565a4410b7f1354505ffaeb92536d
|
|
|
|
| |
00e7d577abb2a5bc75795293bf112baa41fcad78
|
|
|
|
|
|
| |
(build/conf/settings.conf)
869037e1c5f3c8bb6468e9d636b044f167bba6dc
|
|
|
|
| |
d063d388d6659a94f4c78cf5de3275260939bb62
|
|
|
|
|
| |
Fix patching cpp proto
af01597c047856b865c6a4e9933cfeacb0a2f39b
|
|
|
|
|
| |
The TryGetEnv function can be used to distinguish the case when a variable is not defined from the case when it has an empty value.
4aab7a2a39f4b9107b0b1d1ef639dc2c41c04f42
|
| |
|
|
|
|
|
| |
"restricted" should be the only group which allows license properties variation depending on the linkage type.
1a5ba1b3fd4c0e013d4cb1fdac55de5e4c20651f
|
| |
|
|
|
|
|
|
| |
have been found
47942740235036bf82beafb3cfbb952d098b4f9b
|
|
|
|
| |
872de8f38d12966355d1a44327a80fb6ede7e34e
|
|
|
|
| |
d9beae52f9300e65eddec8c2b865f132ea6b5833
|
| |
|
| |
|
|
|
|
| |
dce1a2d8375df9b3baf32973ca156e03dd52cdd0
|
|
|
|
|
| |
Update tools: yexport, os-yexport
b4aafe4da317273315faa80275208d5a4f3fb9ab
|
|
|
|
| |
81235399e4c6e917bcabe929f3897deeb2232bbc
|
|
|
|
| |
e9195292698f6465508db3182b20619c915c1d84
|
|
|
|
| |
99902937b544f5d8150a5c6132861e1bb52d3ced
|
| |
|
|
|
|
| |
1d45d044e90ad310e6e002f8446320e56dcdf6fb
|
|
|
|
| |
bb11084ac0472d18fb06fe65a35363f2e704e1ab
|
|
|
|
| |
ef0cf75a2639c295e45bcb66c3af27554dc3586c
|
|
|
|
|
|
| |
snapshot divergence when rolling 23.2
964925e3330bb2bc336b4c2721370bbd33f05f34
|
|
|
|
| |
8b2fb6d45dd388298c3677e8c0c91486fdb94061
|
|
|
|
| |
0032b463de1c82891fd7b26ae5b2f538c88e0d01
|
|
|
|
| |
d1095d949cece50ea82a07a544cf10ef08a02583
|
|
|
|
| |
e0f2ba4eb69ee69baef77b3eccd7b950eb95c58a
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is quite a bit of diff, so here goes the explanation:
1) interations with c-ares and epoll from ctor/dtor were moved to separate functions so that logical steps are clearer.
2) Same logical separation has been done to ResolverThread routine and some other functions (like, making OnRequestTimeout handler an actual function with human-readable name).
3) Now AresDnsResolver resembles ActionQueue much more in following ways:
3.1) We have a mechanism of shutting down the queue itself. It prevents situations when someone is still overloading resolver queue during the shutdown making thread delay
the shutdown for quite a bit. This logic also allows us to have an easy way of knowing that we have been shut down outside of resolver thread.
3.2) We ensure thread is running before we submit the task. We expect this to slightly improve reactivity of the first task but generally this change is not very needed.
3.3) ResolverThread now always cancels promises if it was stopped. Previously, some of the requests were set with errors, which was quite misleading.
3.4) ResolverThread no longer attempts to drain the entire queue if it was unlucky enough to observe a empty queue previously.
4) When cancelling promises we also cancel their timeout cookies thus we no longer trigger timeouts of already cancelled requests.
Changes 3.3 and 3.4 should ensure reactivity of processing requests and should completely prevent situations when ResolverThread is stuck on processing queue events without looking at c-ares "ready-to-be-executed" callbacks which would otherwise timeout.
fcebf3922e63570e1f82204e902d89859c0cbfe7
|
|
|
|
| |
2806d67a9477e3d51376cd3e16a9b5d6b785806b
|
|
|
|
| |
e71f3730f57e720d6efb18f42adbd2006606844e
|
|
|
|
|
|
|
|
|
|
| |
From hash: [ae2f36cbbf675b89b3938d7adfde039fff703a81](https://a.yandex-team.ru/arcadia/commit/ae2f36cbbf675b89b3938d7adfde039fff703a81)
From revision: [14005177](https://a.yandex-team.ru/arcadia/commit/rXXXXXX)
[CI flow](https://a.yandex-team.ru/projects/ya_make/ci/releases/flow?dir=devtools%2Fya&id=release-ya-bin2-ya-bin3-tts&version=398)
Flow triggered by user: [robot-ci](https://staff.yandex-team.ru/robot-ci)
Update tools: ya_bin3, os_ya, ya_bin, test_tool, os_test_tool
c3e319808fd389f3ad4e85343b8c4e9918f9d49a
|
|
|
|
|
| |
Enable new UIDs for all sanitizer builds (build/conf/settings.conf)
e05e6ba71c10a5a202081b1899b244d696b00dad
|
|
|
|
| |
1d65ab0a1fe5bec1cf34e97c16e4babc53be0c21
|