| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
d2f0cef9da3dea95d992cfd2e5cc4ad96dd8832b
|
| |
|
|
|
|
|
|
| |
clang-cl.
2ec1f20e2dad9f77a50755cc3835d082d172a386
|
|
|
|
|
|
|
| |
socket by default
анонс https://at.yandex-team.ru/clubs/arcadia/30286
77f0f6dfa6c3bc8c2a8428ecf91cd76b22bdb60e
|
|
|
|
| |
78574ec3b29ba6ee7f533860ee9b27c3a91365c2
|
|
|
|
| |
d4d430da9fff0a3f1f57512a35eeb2edfa6a4828
|
|
|
|
| |
e7034cabf97d282830954046742a5be9f4f5a3af
|
|
|
|
|
|
| |
clang-cl on Windows.
32c2f036c7fa256292483963817ceffcbba8059c
|
|
|
|
| |
c70b25e58264f96e168e8032daf67c63d1fdeede
|
|
|
|
| |
b9effdfd19749fe1e0f90f94bac3ca6eff4bc5ad
|
|
|
|
| |
f18a9a891758a7ec308b2a88b2cdf3f0942b2301
|
|
|
|
|
|
| |
version is used.. #2302
0843dd6fab7789634d13bdde50586f8d122288fa
|
| |
|
|
|
|
| |
98477c92ad7634e0c2a1b70c3b9a6d4d53ed8508
|
|
|
|
| |
dc54e7eba29148c2780ac317d35c79b12fa3bd36
|
|
|
|
|
| |
Rename PullConsumer -> PullQueueConsumer
1ec6e386d6a3570532f130b99857a4bc2f20210b
|
| |
|
|
|
|
| |
c7ccedfc57e1b07e11c410c19f907ea8bda24dd3
|
|
|
|
| |
6e07ea929418b1fae4257a2af37aa0ed5799f22a
|
|
|
|
| |
a13d43773645d8c413d919a87fbdc395cead1945
|
|
|
|
| |
68159f3e564ba311e2279bf133e9aa4eef3f099f
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changing the architecture of communication between QT and HTTP/RPC proxies.
**Problem:**
Now we want to support multiple ACOs in a single query. This causes incompatibility between older and newer components. SDK/Proxies/QT. Therefore, we need to update all these components simultaneously, which is not an easy task. A similar problem existed when we added the first version of ACO, and possibly we will have similar problems in future developments.
**Solution:**
Step 1.
Move all complex logic from proxies to QT. After that proxies will simply resend all requests to QT service. And QT will write to state tables.
(This PR)
Step 2
Make it possible to work with RPC requests from different proxy versions. Add support for different versions of the RPC API in the QT proxy server.
(Next PR, together with multiple ACO support)
Step 3
Make it possible to work with requests from different SDK versions in proxies. Add support for different versions of the RPC API in the RPC proxy, and feature flags to the HTTP protocol.
(Next PR, together with multiple ACO support)
**Benefits:**
All communication with QT state tables will take place through the QT service. Therefore, this logic will always be delivered in the same image. This removes all starting incompatibilities and makes it possible to update mentioned components in the next order.
QT->Proxies->SDK
---
da929c1c8bbc437f878c350a2cbd350841ccf8ce
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/591
Co-authored-by: mpereskokova <mpereskokova@yandex-team.com>
|
|
|
|
|
|
|
| |
https://clang.llvm.org/docs/ClangFormatStyleOptions.html#packconstructorinitializers
Just set the default value explicitly.
8c4b172f18d90904f2b2728f43eb56b52ee24f6a
|
|
|
|
| |
1e4862196f95370b4403c48a76688489e6b593c7
|
|
|
|
| |
0a8837e8e30b04fcab64bbb005c2e3233e20e18d
|
|
|
|
|
|
|
|
|
|
| |
From hash: [0cb9e331dfdcd6329e9a8211b4b89e280df9aa03](https://a.yandex-team.ru/arcadia/commit/0cb9e331dfdcd6329e9a8211b4b89e280df9aa03)
From revision: [14134418](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=194)
Flow triggered by user: [robot-ci](https://staff.yandex-team.ru/robot-ci)
Update tools: ymake, os_ymake
79d1103fc0e2a0ce579f6b70af4d118e2bea6a00
|
|
|
|
| |
280befb46d5e3e117f50f938c68bf14c992cd65e
|
|
|
|
| |
8d72a1e5220ffe0bb7a82257f422606184202ad0
|
| |
|
|
|
|
|
| |
YT-21810: Fixed TReconfigurableThroughputThrottler
480384ba8327347af57fac418d7aafdea855febd
|
|
|
|
| |
7604e12fadf99a4ae81fac39d8926d62d66a9c9f
|
|
|
|
| |
54e59afec75240b5f18a03f72ec7a134ae64b1fb
|
|
|
|
| |
da813408128ccc8c4ff8bf77751e68e5d3a10398
|
|
|
|
| |
5c21317137b1e47dc927d919683564f2c959206c
|
|
|
|
| |
e1bd39ae9423633f01b5185703a754aa9e26e3a3
|
|
|
|
|
| |
Keep "Update contrib/libs/lzma to 5.6.1" as an independent commit.
0cb9e331dfdcd6329e9a8211b4b89e280df9aa03
|
|
|
|
|
|
|
| |
https://clang.llvm.org/docs/ClangFormatStyleOptions.html#spacesinsquarebrackets
It looks like this is the default behavior though it is not clear neither from docs, nor from the code.
766f1ca523d39d476416af2a36de7579df7b9ebd
|
|
|
|
| |
0b27f0b7396eefe88b791406529b86b14ac0289b
|
|
|
|
| |
8f2be822acca9aea87fb4504635b81659cd8b3f4
|
|
|
|
|
| |
Fix add extra flags macro
c6799a76432fa0f6035f00438e89ed62b7923c3c
|
|
|
|
| |
feeb90a4704dca0309a6252ea872283ea9302a4b
|
| |
|
|
|
|
| |
59b13027ba48c5397d5826853170e119ebb97ca2
|
|
|
|
| |
cc7935c2b685b0a50941d10fbd53ac5f60c09b3b
|
| |
|
|
|
|
| |
60a062b712a946277218f01266a01df505972b31
|
|
|
|
| |
c41fbbb00f2c7073216591393f2c0623d50f5fcb
|
|
|
|
| |
acf509f8d132be218f69d69fb8223c0c8b77f765
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added static analysis to format of YT_LOG_XXX macro's. We expect you to write format string as first or the second argument and follow the rules as if you are writing arguments for `NYT::Format`, which match those of printf: https://en.cppreference.com/w/cpp/io/c/fprintf plus few extra flags like 'v'. At the moment analyser checks if flags sequences is
1. Correctly terminated
2. Only contains specifiers valid for a given argument (if we are parsing nth argument of type T, then T must have all specifiers from its list of Conversion or Flag specifiers.
(2) Also means that the number of flag sequences must match the number of arguments supplied to format.
You can specialize `TFormatArg<T>` which is used to determine allowed Conversion and Flag specifiers to customise rules of static analysis. E.g. you can introduce new flags to the mix which you promise to parse in the related FormatValue function.
If you feel like this produces to much overhead in terms of compile time, you are free to use macro YT_DISABLE_FORMAT_STATIC_ANALYSIS to turn the entire thing into a no-op. We have measured compile time to be affected by roughly 3-5% in a log intensive files.
ae6def509474e8a42027bb4ed84ac040509b7c85
|