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.15](backport #40144) x-pack/filebeat/input/{cel,salesforce}: check response for nilness before logging #40159

Merged
merged 2 commits into from
Jul 23, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jul 9, 2024

Proposed commit message

It turns out that retryablehttp will pass a nil *http.Response to the client's ErrorHandler function although this is not documented. In the cases where we are using this, this will result in a nil deference panic when the retries exceed their maximum. So, check for nilness to avoid this.

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

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs


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

…fore logging (#40144)

It turns out that retryablehttp will pass a nil *http.Response to the
client's ErrorHandler function although this is not documented. In the
cases where we are using this, this will result in a nil deference
panic when the retries exceed their maximum. So, check for nilness to
avoid this.

(cherry picked from commit b056515)
@mergify mergify bot requested a review from a team as a code owner July 9, 2024 21:21
@mergify mergify bot added the backport label Jul 9, 2024
@mergify mergify bot requested a review from a team as a code owner July 9, 2024 21:21
@mergify mergify bot assigned efd6 Jul 9, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jul 9, 2024
@botelastic
Copy link

botelastic bot commented Jul 9, 2024

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

Copy link
Contributor Author

mergify bot commented Jul 15, 2024

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

1 similar comment
Copy link
Contributor Author

mergify bot commented Jul 22, 2024

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

Copy link
Contributor Author

mergify bot commented Jul 23, 2024

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/8.15/pr-40144 upstream/mergify/bp/8.15/pr-40144
git merge upstream/8.15
git push upstream mergify/bp/8.15/pr-40144

@andrewkroh andrewkroh enabled auto-merge (squash) July 23, 2024 14:15
@andrewkroh andrewkroh merged commit c5c2c56 into 8.15 Jul 23, 2024
16 of 19 checks passed
@andrewkroh andrewkroh deleted the mergify/bp/8.15/pr-40144 branch July 23, 2024 15:57
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.

3 participants