Skip to content
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

Reduce the goroutine in flowgraph to 2 #27727

Closed
wants to merge 1 commit into from

Conversation

smellthemoon
Copy link
Contributor

#24826
/kind improvement

@sre-ci-robot sre-ci-robot added the kind/improvement Changes related to something improve, likes ut and code refactor label Oct 16, 2023
@sre-ci-robot sre-ci-robot added the size/S Denotes a PR that changes 10-29 lines. label Oct 16, 2023
@sre-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: smellthemoon
To complete the pull request process, please assign wxyucs after the PR has been reviewed.
You can assign the PR to them by writing /assign @wxyucs in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mergify mergify bot added the dco-passed DCO check passed. label Oct 16, 2023
@mergify
Copy link
Contributor

mergify bot commented Oct 16, 2023

@smellthemoon ut workflow job failed, comment rerun ut can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 16, 2023

@smellthemoon E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 17, 2023

@smellthemoon E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

internal/datanode/data_sync_service.go Outdated Show resolved Hide resolved
internal/util/flowgraph/node.go Outdated Show resolved Hide resolved
@sre-ci-robot sre-ci-robot added size/M Denotes a PR that changes 30-99 lines. and removed size/S Denotes a PR that changes 10-29 lines. labels Oct 23, 2023
@mergify
Copy link
Contributor

mergify bot commented Oct 23, 2023

@smellthemoon ut workflow job failed, comment rerun ut can trigger the job again.

@sre-ci-robot sre-ci-robot added area/dependency Pull requests that update a dependency file size/L Denotes a PR that changes 100-499 lines. and removed size/M Denotes a PR that changes 30-99 lines. labels Oct 24, 2023
@smellthemoon smellthemoon force-pushed the goroutine-limit branch 5 times, most recently from 9cb4675 to 4e203f7 Compare October 24, 2023 12:47
@mergify
Copy link
Contributor

mergify bot commented Oct 24, 2023

@smellthemoon E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 24, 2023

@smellthemoon ut workflow job failed, comment rerun ut can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 25, 2023

@smellthemoon E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 25, 2023

@smellthemoon ut workflow job failed, comment rerun ut can trigger the job again.

@mergify
Copy link
Contributor

mergify bot commented Oct 31, 2023

@smellthemoon E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 1, 2023

@smellthemoon E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 1, 2023

@smellthemoon ut workflow job failed, comment rerun ut can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 1, 2023

@smellthemoon E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 1, 2023

@smellthemoon ut workflow job failed, comment rerun ut can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 1, 2023

@smellthemoon E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 1, 2023

@smellthemoon ut workflow job failed, comment rerun ut can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 2, 2023

@smellthemoon E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 2, 2023

@smellthemoon ut workflow job failed, comment rerun ut can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 3, 2023

@smellthemoon E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 3, 2023

@smellthemoon ut workflow job failed, comment rerun ut can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 7, 2023

@smellthemoon ut workflow job failed, comment rerun ut can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 7, 2023

@smellthemoon E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 7, 2023

@smellthemoon ut workflow job failed, comment rerun ut can trigger the job again.

Copy link
Contributor

mergify bot commented Nov 7, 2023

@smellthemoon E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@mergify mergify bot added needs-dco DCO is missing in this pull request. and removed dco-passed DCO check passed. labels Apr 24, 2024
Copy link
Contributor

mergify bot commented Apr 24, 2024

@smellthemoon Thanks for your contribution. Please submit with DCO, see the contributing guide https://github.com/milvus-io/milvus/blob/master/CONTRIBUTING.md#developer-certificate-of-origin-dco.

Copy link
Contributor

mergify bot commented Apr 24, 2024

@smellthemoon

Invalid PR Title Format Detected

Your PR submission does not adhere to our required standards. To ensure clarity and consistency, please meet the following criteria:

  1. Title Format: The PR title must begin with one of these prefixes:
  • feat: for introducing a new feature.
  • fix: for bug fixes.
  • enhance: for improvements to existing functionality.
  • test: for add tests to existing functionality.
  • doc: for modifying documentation.
  • auto: for the pull request from bot.
  1. Description Requirement: The PR must include a non-empty description, detailing the changes and their impact.

Required Title Structure:

[Type]: [Description of the PR]

Where Type is one of feat, fix, enhance, test or doc.

Example:

enhance: improve search performance significantly 

Please review and update your PR to comply with these guidelines.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependency Pull requests that update a dependency file do-not-merge/invalid-pr-format kind/improvement Changes related to something improve, likes ut and code refactor needs-dco DCO is missing in this pull request. size/L Denotes a PR that changes 100-499 lines.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants