Add changelog for fix Acquire(): requirement result == 0 failed in ydb tools restore
#29493
Conversation
|
🟢 |
|
⚪
🟢 |
|
⚪
🟢 |
There was a problem hiding this comment.
Pull request overview
This PR adds a changelog entry documenting a bug fix for the ydb tools restore command that could crash due to a mutex lock failure caused by an internal race condition. The fix was implemented in PR #29462.
- Adds a new changelog entry describing the bug fix for the restore command crash
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| * Added a new `--output` option to the `ydb admin cluster state fetch` command. The new option specify path to the output .tar.bz2 file. | ||
| * Added a simple progress bar for non-interactive stderr. | ||
| * Added a new `omit-indexes` property to the `--item` option of the `ydb tools copy` command, allowing tables to be copied without their indexes. | ||
| * Fixed a bug where the `ydb tools restore` command could crash with an `mutex lock failure (Invalid argument)` error due to an internal race condition. |
There was a problem hiding this comment.
Grammar error: Should be "a mutex lock failure" instead of "an mutex lock failure" because "mutex" starts with a consonant sound.
| * Fixed a bug where the `ydb tools restore` command could crash with an `mutex lock failure (Invalid argument)` error due to an internal race condition. | |
| * Fixed a bug where the `ydb tools restore` command could crash with a `mutex lock failure (Invalid argument)` error due to an internal race condition. |
2 participants
Changelog category
Description for reviewers
For #29462