Skip to content

[8.6](backport #34647) Add SafeProcessor wrapper#34665

Merged
rdner merged 1 commit into8.6from
mergify/bp/8.6/pr-34647
Feb 27, 2023
Merged

[8.6](backport #34647) Add SafeProcessor wrapper#34665
rdner merged 1 commit into8.6from
mergify/bp/8.6/pr-34647

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Feb 24, 2023

This is an automatic backport of pull request #34647 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

Each processor might end up in multiple processor groups.
Every group has its own `Close` that calls `Close` on each
processor of that group which leads to multiple `Close` calls
on the same processor.

If the `SafeProcessor` wrapper was not used,
the processor would have to handle multiple `Close` calls with
adding `sync.Once` in its `Close` function.

We make it easer for processor developers and take care of it
in the processor registry instead.

(cherry picked from commit 5007b58)
@mergify mergify bot requested a review from a team as a code owner February 24, 2023 16:05
@mergify mergify bot requested review from fearful-symmetry and rdner and removed request for a team February 24, 2023 16:05
@mergify mergify bot added the backport label Feb 24, 2023
@mergify mergify bot assigned rdner Feb 24, 2023
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 24, 2023
@botelastic
Copy link
Copy Markdown

botelastic bot commented Feb 24, 2023

This pull request doesn't have a Team:<team> label.

@rdner
Copy link
Copy Markdown
Member

rdner commented Feb 24, 2023

There will be no more 8.6 releases.

@rdner rdner closed this Feb 24, 2023
@mergify mergify bot deleted the mergify/bp/8.6/pr-34647 branch February 24, 2023 16:06
@rdner rdner restored the mergify/bp/8.6/pr-34647 branch February 27, 2023 08:10
@rdner rdner reopened this Feb 27, 2023
@mergify
Copy link
Copy Markdown
Contributor Author

mergify bot commented Feb 27, 2023

This pull request has not been merged yet. Could you please review and merge it @rdner? 🙏

@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-02-27T08:11:19.766+0000

  • Duration: 72 min 20 sec

Test stats 🧪

Test Results
Failed 0
Passed 25040
Skipped 1959
Total 26999

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@rdner rdner merged commit d6fe3a0 into 8.6 Feb 27, 2023
@rdner rdner deleted the mergify/bp/8.6/pr-34647 branch February 27, 2023 09:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport needs_team Indicates that the issue/PR needs a Team:* label

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants