-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Cherry pick #62840 to 23.8: Fix crash in function formatRow
with JSON
format and HTTP interface
#62855
Conversation
Fix crash in function `formatRow` with `JSON` format and HTTP interface
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h59m41s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h0m17s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h59m51s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h59m59s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d25h0m9s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h59m39s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h0m9s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h58m6s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h0m17s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h3m44s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h57m50s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h59m56s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d25h1m10s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h0m2s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h59m50s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h0m36s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h2m52s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h56m10s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d25h1m19s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h57m52s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h59m32s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h5m3s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h59m17s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h57m21s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h57m2s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h3m41s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h56m31s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h1m24s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h0m24s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h1m24s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h0m27s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h57m44s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h2m6s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h57m57s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Dear @alexey-milovidov, @CurtizJ, the PR is not updated for 1d24h0m40s. Please, either resolve the conflicts, or close it to finish the backport process of #62840 |
Original pull-request #62840
This pull-request is a first step of an automated backporting.
It contains changes similar to calling
git cherry-pick
locally.If you intend to continue backporting the changes, then resolve all conflicts if any.
Otherwise, if you do not want to backport them, then just close this pull-request.
The check results does not matter at this step - you can safely ignore them.
Note
This pull-request will be merged automatically. Please, do not merge it manually (but if you accidentally did, nothing bad will happen).
Troubleshooting
If the PR was manually reopened after being closed
If this PR is stuck (i.e. not automatically merged after one day), check #62840 for
pr-backports-created
label and delete it.Manually merging will do nothing. The
pr-backports-created
label prevents the original PR #62840 from being processed.If the conflicts were resolved in a wrong way
If this cherry-pick PR is completely screwed by a wrong conflicts resolution, and you want to recreate it:
pr-cherrypick
label from the PRYou also need to check the original PR #62840 for
pr-backports-created
, and delete if it's presented there