New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Try update protobuf to 3.17.3 #26424
Conversation
What is the motivation for this update? |
Minimize commits that present in Extras but not yet in upstream. Some changes collapse but in some cases I'm going to detect cases where we have not sent changes to upstream. |
@Mergifyio rebase |
Command
|
FYI to debug errors in QEMU there is special integration with remote gdb:
In gdb you can see
|
@Mergifyio update |
Command
|
* master: (482 commits) ru version colon en version colon Attempt to fix flaky 00705_drop_create_merge_tree Help with ClickHouse#26424 Adjust 00537_quarters to be timezone independent Add a codec AES_128_GCM_SIV for encrypting columns on disk (ClickHouse#19896) Update BaseDaemon.cpp Update PULL_REQUEST_TEMPLATE.md edits after review small fix in links Make the test parallelizable ru version edit ru version en version Fix 01600_quota_by_forwarded_ip typo Remove trailing whitespaces from docs Remove trailing whitespaces from docs fix system.zookeeper_log initialization Move formatBlock to its own file ... # Conflicts: # programs/server/Server.cpp
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Updated protobuf to 3.17.3. Changelogs are available on https://github.com/protocolbuffers/protobuf/releases
Detailed description / Documentation draft:
...
By adding documentation, you'll allow users to try your new feature immediately, not when someone else will have time to document it later. Documentation is necessary for all features that affect user experience in any way. You can add brief documentation draft above, or add documentation right into your patch as Markdown files in docs folder.
If you are doing this for the first time, it's recommended to read the lightweight Contributing to ClickHouse Documentation guide first.
Information about CI checks: https://clickhouse.tech/docs/en/development/continuous-integration/