Skip to content

[8.13](backport #37738) x-pack/filebeat/input/httpjson: Fix parseDate location offset #38085

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

Merged
merged 5 commits into from
Mar 6, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 21, 2024

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

Add a new value template helper `parseDateInTZ` where users can apply the proper timezone when parsing dates, avoiding the limitations of `parseDate` with timezone abbreviations. It accepts numeric offsets and IANA time zone names.

(cherry picked from commit 8214f9f)
@mergify mergify bot requested a review from a team as a code owner February 21, 2024 14:28
@mergify mergify bot added the backport label Feb 21, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 21, 2024
@botelastic
Copy link

botelastic bot commented Feb 21, 2024

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

@elasticmachine
Copy link
Collaborator

elasticmachine commented Feb 21, 2024

💚 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

  • Duration: 136 min 33 sec

❕ Flaky test report

No test was executed to be analysed.

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

@chemamartinez
Copy link
Contributor

@Mergifyio refresh

Copy link
Contributor Author

mergify bot commented Feb 22, 2024

refresh

✅ Pull request refreshed

@chemamartinez
Copy link
Contributor

@Mergifyio rebase

Copy link
Contributor Author

mergify bot commented Feb 22, 2024

rebase

❌ Unable to rebase: user chemamartinez is unknown.

Please make sure chemamartinez has logged in Mergify dashboard.

Copy link
Contributor Author

mergify bot commented Feb 26, 2024

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

Copy link
Contributor Author

mergify bot commented Mar 4, 2024

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

Copy link
Contributor Author

mergify bot commented Mar 4, 2024

refresh

✅ Pull request refreshed

@chemamartinez chemamartinez merged commit 8409f2c into 8.13 Mar 6, 2024
21 checks passed
@chemamartinez chemamartinez deleted the mergify/bp/8.13/pr-37738 branch March 6, 2024 15:39
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