| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
commit_hash:39c670927995d2e5558f218e3d198f29a2e2af40
|
|
|
|
| |
commit_hash:14cd0f852fd43d48ad01a7f6608504ef16a4ac95
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- [x] Chained futures, add `CompleteAsync` method (then will migrate the YDB CLI on it).
- [x] Removed deadlined and fallback NameService as unused
- [x] Annotate thread-safe methods with `const` and use `AtomicSharedPtr` for them.
- [x] Move `name` to `name/service` with backward compatibility with the YDB CLI.
---
`CompletionEngine` is left thread-unsafe because of the dependency chain `CompletionEngine -> LocalSyntaxAnalysis -> C3Engine` which is thread-unsafe, but readonly indexed data structures such as `Ranking` and `NameService` are annotated with const and distributed via shared pointers.
I removed deadlined and fallback name services because the first is stupid the second is ahead of its time and is better to be added later to keep interfaces as minimal as possible.
---
The migration on async complete plan:
1. Introduce CompleteAsync
2. Migrate clients on CompleteAsync
3. Make Complete to return Future
4. Migrate clients on Complete
5. Remove CompleteAsync
---
- Related to https://github.com/ydb-platform/ydb/issues/9056
- Related to https://github.com/vityaman/ydb/issues/33
- Related to https://github.com/vityaman/ydb/issues/31
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1241
Co-authored-by: vvvv <vvvv@yandex-team.com>
Co-authored-by: vvvv <vvvv@yandex-team.com>
commit_hash:497cc081ab78bebf7354e0acfaa418d936cc8240
|
|
|
|
| |
commit_hash:662bf10e4c8caa4c7310317eacd39715dbadc691
|
|
|
|
| |
commit_hash:4d256df3cba483ed480b07058d40dc2771082b86
|
|
|
|
|
|
|
|
|
|
|
| |
* Changelog entry
Type: feature
Component: controller-agent
Add new delivery fenced connection that works on vanilla linux kernel. It may be used for cpu intensive or gpu jobs to prevent job abort on interruption.
commit_hash:02e0f41ad907dfe1c11defc5439214e31ea12ad5
|
|
|
|
| |
commit_hash:2e0d520af978a9a16495ac4fd2adc8f072ed973a
|
|
|
|
|
|
|
|
| |
* Changelog entry
Type: fix
Component: misc-server
Tablet nodes used to not validate erasure coding. This is now fixed.
commit_hash:c87b15794e5b904cf5876e3887af9aed62b650bc
|
|
|
|
| |
commit_hash:4149625a81c51af40642fe498a887608cc57305f
|
|
|
|
| |
commit_hash:5f4bdb090c2f60459073e3e95ccd39ec58b95232
|
|
|
|
| |
commit_hash:99750816a334658ecd2f306d4a496865e7fcc4d8
|
|
|
|
| |
commit_hash:a2ae9e9ddb0ebd0f3ce876aa1f8f29e291d3aed1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
yajl_tree_parse function
### Changelog entry
...
### Changelog category
* Bugfix
### Description for reviewers
This PR fixes a security vulnerability in yajl\_tree\_parse() that was cloned from yaml but did not receive the security patch. The original issue was reported and fixed under [likema/yajl@31531a6](https://github.com/likema/yajl/commit/31531a6e6b5641398237ce15b7e62da02d975fc6).
This PR applies the same patch to eliminate the vulnerability.
References
[GHSA-cqgm-m7h3-xgwm](https://github.com/advisories/GHSA-cqgm-m7h3-xgwm "GHSA-cqgm-m7h3-xgwm")
<https://nvd.nist.gov/vuln/detail/CVE-2023-33460>
[likema/yajl@31531a6](https://github.com/likema/yajl/commit/31531a6e6b5641398237ce15b7e62da02d975fc6)
---
Pull Request resolved: <https://github.com/ydb-platform/ydb/pull/17570>
commit_hash:d022109c9836673d185db1ffab7e1064ab8f561d
|
|
|
|
| |
commit_hash:5065ec89aed827ce2d112d5f8623dfb0215a5207
|
|
|
|
| |
commit_hash:9feae42eea92837e800e65cbcf9acc15f580e438
|
|
|
|
|
|
|
|
|
| |
No description
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1240
commit_hash:9afd1a8a5e8a67c4618712edca143bb56027764f
|
|
|
|
|
| |
Use junit4/5 semantics for java tests
commit_hash:def6b37d434f8759c3ba83213b5baf2f1af85220
|
|
|
|
| |
commit_hash:f2e6589626879ba465833a71e6d23df856f201c9
|
|
|
|
| |
commit_hash:f3bb066b14d05257ef5fe43c4f80a92a16c10b4a
|
|
|
|
| |
commit_hash:47af8407e2e454dd37342ff0a8e7d638e1d5f4a6
|
|
|
|
| |
commit_hash:f8138b2300bb8c3beed8d27d4688beb4dc2c6f3a
|
|
|
|
| |
commit_hash:b561940fa34bb32aa7a67fa8522fb39ffe55d141
|
|
|
|
| |
commit_hash:ae46d476745bcde01f2465ccfec1ae45e8d29d1e
|
|
|
|
| |
commit_hash:f775e1468b8181bc7f7f409dde6a1af284725e68
|
|
|
|
| |
commit_hash:7579cfab3b598d951714e83b74e02d1d9b23cec2
|
|
|
|
| |
commit_hash:188eabb32fe62c00b28fbfd2ca438d751e66a540
|
|
|
|
| |
commit_hash:dc3193604b8e3f1c1a2e012318f542b2497d7638
|
|
|
|
|
| |
Update tools: test_tool, os_ya, ya_bin, os_test_tool
commit_hash:e1a9b4c4ac2cb1d4372a80cdaf9ff5ffad68f9f1
|
|
|
|
| |
commit_hash:e4127882c960fab8e539f5332c981e7adebc5cb5
|
|
|
|
| |
commit_hash:a97752fe47c21a472a780e6b2097cd7c20c63766
|
|
|
|
| |
commit_hash:66a9427951da5b22e74fc6c04f4a3b7fd8713510
|
|
|
|
| |
commit_hash:f557fe6f4960cb4466290d49e5f14af379ba2f94
|
|
|
|
| |
commit_hash:305fec3efc9087bab26ae2fca809e1c3c0723b00
|
|
|
|
|
| |
Remove semantics from EXTERNAL_JAVA_LIBRARY
commit_hash:30f823498fa04c4da5d137a99e1d24e15e7d5b93
|
|
|
|
| |
commit_hash:9b9fa862d523687c3eb883e9b94c2ecef522cda8
|
|
|
|
| |
commit_hash:065881aad5e9f774c9709037fdfd30b5d3c77d51
|
|
|
|
| |
commit_hash:2b01b1b2387f71903fc29f3364d1e5f46f35a703
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When I tried to implement a folder and object names completion at `ID_QUOTED` I faced with a problem, that I actually can't detect, that cursor is at `ID_QUOTED` token because `TCompletionInput::Text` it was cut until the `TCompletionInput::CursorPosition`, therefore at input ``` SELECT * FROM `#` ``` prefix was ``` SELECT * FROM `# ``` and then lexer failed.
While we actually want tokenize the whole current statement, `C3` still needs to receive a prefix as input. I tried to tokenize the whole statement and then on input `SELECT Optional<#>` got nothing because `<>` is solid token in the `SQL`. The only way to fix it I found is to cut a query to prefix until the cursor position.
BTW, current implementation is not so efficient as we tokenize the input multiple times. Especially `SplitQueryToStatemnts` seems heavy. In future we anyway will parse the whole input so will need to design APIs to receive ready token streams to do statements splitting, for example, just not to do the work twice.

So I introduce you the following changes
- [x] Select the whole current statement, not just prefix.
- [x] Find the token at caret and output no candidates when caret is at `STRING_VALUE`, `DIGIGTS` and so on.
- [x] Change `C3` wrapper interface to take `TCompletionInput` to hide an implementation detail that it runs on cut prefix.
- [x] `#` annotated queries in unit tests.
- [x] Detect `CaretTokenPosition` -- if is it enclosed with a token or between two.
- [x] Ensure that `maxErrors` in `ILexer::Tokenize` is positive. Just a tiny bugfix.
---
- Related to https://github.com/ytsaurus/ytsaurus/pull/1209
- Related to https://github.com/ydb-platform/ydb/issues/9056
- Related to https://github.com/vityaman/ydb/issues/14
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1225
commit_hash:a434b9888ec8a7356247d63d9f1420e256ae4fca
|
|
|
|
| |
commit_hash:f4f2e8b9ba31109593c94251f64e1061f00af304
|
|
|
|
| |
commit_hash:13b88581d861a38841bc1473ddb1ad07befea7ec
|
|
|
|
| |
commit_hash:09465895d52261f981de0dac35d5792dbf8d9b59
|
|
|
|
|
| |
https://github.com/yandex/toolchain-registry/releases/tag/clang18-v9
commit_hash:0c8b52ff29b719af33002f537095864d5c8e1aaf
|
|
|
|
| |
commit_hash:cc8e1d7c04d38c7d9f7d42a6f6f327c73ba11502
|
|
|
|
| |
commit_hash:5c78798b304a05a90b7e9a5b2bcdc1d3454d9f77
|
|
|
|
| |
commit_hash:4eeebcfb3a5a301157ffdf1f6fb562be65cc3011
|
|
|
|
| |
commit_hash:f6bb35748ba86b6c9a4a308231cf2ae10f1eeac7
|
|
|
|
| |
commit_hash:5117342b91cba57f7c45d262b1c95aea6a65061a
|
|
|
|
| |
commit_hash:df494d98a61d65d0b77b335f1e998670be2f9f2b
|
|
|
|
| |
commit_hash:ca0a881f294c00b673673335c9366699c4be7c86
|
|
|
|
| |
commit_hash:a1f6e10ba4e2df5b1e0a7e49410e245ed7b92ae3
|