Skip to content

[8.17](backport #44342) [filebeat][streaming] - Fixed a websocket panic scenario which would occur after exhausting max retries #44389

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
Merged
merged 2 commits into from
May 20, 2025
Merged

[8.17](backport #44342) [filebeat][streaming] - Fixed a websocket panic scenario which would occur after exhausting max retries #44389

merged 2 commits into from
May 20, 2025
+18 −8

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented May 20, 2025

Type of change

  • Bug

Proposed commit message

In some scenarios the websocket response object can become nil and
cause  certain logging statements to cause an unexpected panic. This PR
fixes once  such identified scenario.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

None

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

This is an automatic backport of pull request #44342 done by [Mergify](https://mergify.com).

@ShourieG @mergify
[filebeat][streaming] - Fixed a websocket panic scenario which would …
f60d7e4 
…occur after exhausting max retries (#44342)

In some scenarios the websocket response object can become nil and
cause  certain logging statements to cause an unexpected panic. This PR
fixes once  such identified scenario.

(cherry picked from commit f6994c0)
@mergify mergify bot requested a review from a team as a code owner May 20, 2025 07:19
@mergify mergify bot added the backport label May 20, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 20, 2025
@botelastic
Copy link

botelastic bot commented May 20, 2025

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

@ShourieG
Copy link
Contributor

/test

@ShourieG ShourieG merged commit 74c8625 into 8.17 May 20, 2025
22 of 25 checks passed
@ShourieG ShourieG deleted the mergify/bp/8.17/pr-44342 branch May 20, 2025 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ShourieG ShourieG ShourieG approved these changes

Assignees

@ShourieG ShourieG

Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@ShourieG