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

[8.4](backport #823) Fix/panic with composable renderer #894

Merged
merged 1 commit into from
Aug 10, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Aug 10, 2022

This is an automatic backport of pull request #823 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

* Fix a panic with wg passed to the composable object

In the code to retrieve the variables from the configuration files we
need to pass a execution callback, this callback will be called in a
goroutine. This callback can be executed multiple time until the
composable renderer is stopped. There were a problem in the code that
made the callback called multiple time and it made the waitgroup
internal counter to do to a negative values.

This commit change the behavior, it start the composable renderer give
it a callback when the callback receives the variables it will stop the
composable's Run method using the context.

This ensure that the callback will be called a single time and that the
variables are correctly retrieved.

Fixes: #806
(cherry picked from commit 56787a6)
@mergify mergify bot requested a review from a team as a code owner August 10, 2022 13:50
@mergify mergify bot added the backport label Aug 10, 2022
@mergify mergify bot assigned ph Aug 10, 2022
@mergify mergify bot requested review from aleksmaus and michalpristas and removed request for a team August 10, 2022 13:50
@elasticmachine
Copy link
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: 2022-08-10T13:50:32.186+0000

  • Duration: 19 min 5 sec

Test stats 🧪

Test Results
Failed 0
Passed 6134
Skipped 23
Total 6157

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

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

  • /test : Re-trigger the build.

  • /package : Generate the packages.

  • run integration tests : Run the Elastic Agent Integration tests.

  • run end-to-end tests : Generate the packages and run the E2E Tests.

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

@elasticmachine
Copy link
Contributor

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 97.26% (71/73) 👍
Files 67.857% (152/224) 👍
Classes 68.161% (304/446) 👍
Methods 51.831% (835/1611) 👍
Lines 38.316% (9104/23760) 👍 0.021
Conditionals 100.0% (0/0) 💚

@ph ph merged commit 0eeecb5 into 8.4 Aug 10, 2022
@mergify mergify bot deleted the mergify/bp/8.4/pr-823 branch August 10, 2022 18:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants