Skip to content

[cherry-pick][branch-2.11]Cherry-pick three PR to branch-2.11 - #19833

Closed
liangyepianzhou wants to merge 1 commit into
branch-2.11from
three_PR
Closed

[cherry-pick][branch-2.11]Cherry-pick three PR to branch-2.11#19833
liangyepianzhou wants to merge 1 commit into
branch-2.11from
three_PR

Conversation

@liangyepianzhou

Copy link
Copy Markdown
Contributor

Motivation

Cherry-pick three PR to branch-2.11:

Verifying this change

  • Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

  • Added integration tests for end-to-end deployment with large payloads (10MB)
  • Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

  • Dependencies (add or upgrade a dependency)
  • The public API
  • The schema
  • The default values of configurations
  • The threading model
  • The binary protocol
  • The REST endpoints
  • The admin CLI options
  • The metrics
  • Anything that affects deployment

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

Matching PR in forked repository

PR in forked repository:

@github-actions github-actions Bot added the doc-not-needed Your PR changes do not impact docs label Mar 16, 2023
@codelipenghui
codelipenghui deleted the three_PR branch April 4, 2023 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc-not-needed Your PR changes do not impact docs ready-to-test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant