Cherry-pick: Backport #85440 to 24.8: Fix possible UB in case of MEMORY_LIMIT_EXCEEDED during String deserialization - #2088
Conversation
Backport ClickHouse#85440 to 24.8: Fix possible UB in case of MEMORY_LIMIT_EXCEEDED during String deserialization
|
This is an automated comment for commit dd86c51 with description of existing statuses. It's updated for the latest CI running ❌ Click here to open a full report in a separate page
Successful checks
|
CI triage — 1 real failure, and it's not a code/test problemVerdict: 2 red checks, both trace to the same root cause. 0 test/build failures, 1 process failure (DCO), and the
DCO (the only substantive failure)The cncf/dco2 app reports:
The single commit on this branch ( Suggested fix (needs a history rewrite of the head commit, so it's yours to run — I don't force-push): git checkout releasy/port/pr-85692-3718c4
git commit --amend --signoff
git push --force-with-lease origin releasy/port/pr-85692-3718c4Alternatively, cncf/dco2 accepts a remediation commit (a non-rewrite option) if you'd rather not force-push — see the "add remediation commit" link in the DCO check output. If you want, tell me to open it as a separate
|
Cherry-picked from ClickHouse#85692.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
Fix possible UB (crashes) in case of MEMORY_LIMIT_EXCEEDED during String deserialization (ClickHouse#85440 by @azat)
CI/CD Options
Exclude tests:
Regression jobs to run: