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

bug Fix 34492 - GCS input format issue #34619

Closed
wants to merge 5 commits into from
Closed

Conversation

gks9128
Copy link

@gks9128 gks9128 commented Feb 20, 2023

Bug

What does this PR do?

Why is it important?

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.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

@gks9128 gks9128 requested a review from a team as a code owner February 20, 2023 16:22
@gks9128 gks9128 requested review from cmacknz and fearful-symmetry and removed request for a team February 20, 2023 16:22
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 20, 2023
@cla-checker-service
Copy link

cla-checker-service bot commented Feb 20, 2023

❌ Author of the following commits did not sign a Contributor Agreement:
, 74bd584, 7ab75c9, 08d454d, 29138b9

Please, read and sign the above mentioned agreement if you want to contribute to this project

@mergify
Copy link
Contributor

mergify bot commented Feb 20, 2023

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @GaurvKumar? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@mergify mergify bot mentioned this pull request Feb 20, 2023
6 tasks
@elasticmachine
Copy link
Collaborator

elasticmachine commented Feb 20, 2023

❕ Build Aborted

The PR is not allowed to run in the CI yet

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Start Time: 2023-02-23T09:26:18.097+0000

  • Duration: 5 min 36 sec

Steps errors 2

Expand to view the steps failures

Load a resource file from a library
  • Took 0 min 0 sec . View more details here
  • Description: approval-list/elastic/beats.yml
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: githubApiCall: The REST API call https://api.github.com/orgs/elastic/members/GaurvKumar return the message : java.lang.Exception: httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/GaurvKumar : httpRequest: Failure connecting to the service https://api.github.com/orgs/elastic/members/GaurvKumar : Code: 404Error: {"message":"User does not exist or is not a member of the organization","documentation_url":"https://docs.github.com/rest/reference/orgs#check-organization-membership-for-a-user"}

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

@cmacknz cmacknz added the Team:Cloud-Monitoring Label for the Cloud Monitoring team label Feb 22, 2023
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Feb 22, 2023
@cmacknz cmacknz requested review from a team and removed request for cmacknz and fearful-symmetry February 22, 2023 18:27
@ShourieG
Copy link
Contributor

Closing this PR as the proper fix is already there in another PR - #34659

@ShourieG ShourieG closed this Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Cloud-Monitoring Label for the Cloud Monitoring team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants