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.

Sign up for GitHub

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

Jump to bottom

[7.17](backport #35820) Fix panic when MaxRetryInterval is specified, but RetryInterval is not #35838

Merged
merged 1 commit into from
Jun 20, 2023
Merged

[7.17](backport #35820) Fix panic when MaxRetryInterval is specified, but RetryInterval is not #35838

merged 1 commit into from
Jun 20, 2023

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jun 20, 2023 •
edited by zube bot
Loading

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

@tibordp @mergify
Fix panic when MaxRetryInterval is specified, but RetryInterval is not (
459a154 
#35820)

* Fix panic when MaxRetryInterval is specified, but RetryInterval is not

* add changelog

(cherry picked from commit 3b73003)
@mergify mergify bot requested a review from a team as a code owner June 20, 2023 19:13
@mergify mergify bot requested review from belimawr and removed request for a team June 20, 2023 19:13
@mergify mergify bot added the backport label Jun 20, 2023
@mergify mergify bot requested a review from faec June 20, 2023 19:14
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jun 20, 2023
@faec faec self-assigned this Jun 20, 2023
@faec faec added the Team:Elastic-Agent Label for the Agent team label Jun 20, 2023
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jun 20, 2023
@elasticmachine
Copy link
Collaborator

💚 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-06-20T19:14:16.357+0000

  • Duration: 91 min 38 sec

Test stats 🧪

Test Results
Failed 0
Passed 22362
Skipped 1420
Total 23782

💚 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!)

@faec faec merged commit 2235c96 into 7.17 Jun 20, 2023
@faec faec deleted the mergify/bp/7.17/pr-35820 branch June 20, 2023 20:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@belimawr belimawr Awaiting requested review from belimawr belimawr is a code owner automatically assigned from elastic/elastic-agent-data-plane

@faec faec Awaiting requested review from faec faec is a code owner automatically assigned from elastic/elastic-agent-data-plane

Assignees

@faec faec

Labels
backport Team:Elastic-Agent Label for the Agent team
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@elasticmachine @faec @tibordp