Skip to content

fix(auditbeat): use correct filetimes field names in some systems#41038

Merged
kruskall merged 1 commit intoelastic:mainfrom
kruskall:fix/auditbeat-filetimes
Apr 18, 2025
Merged

fix(auditbeat): use correct filetimes field names in some systems#41038
kruskall merged 1 commit intoelastic:mainfrom
kruskall:fix/auditbeat-filetimes

Conversation

@kruskall
Copy link
Member

@kruskall kruskall commented Sep 28, 2024

Proposed commit message

fix compile errors on non-linux and openbsd systems

syscall.Stat_t field names is not consistent in different goos causing compile errors on openbsd and non-linux systems

openbsd/riscv still fails to compile but should be fixed once #40132 is merged

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

build auditbeat with GOOS=openbsd GOARCH=amd64 go build .

Related issues

Use cases

Screenshots

Logs

fix compile errors on non-linux and openbsd systems

syscall.Stat_t field names is not consistent in different goos causing
compile errors on openbsd and non-linux systems
@kruskall kruskall requested a review from a team as a code owner September 28, 2024 15:38
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Sep 28, 2024
@botelastic
Copy link

botelastic bot commented Sep 28, 2024

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

@mergify
Copy link
Contributor

mergify bot commented Sep 28, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @kruskall? 🙏.
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-8./d is the label to automatically backport to the 8./d branch. /d is the digit

@mergify
Copy link
Contributor

mergify bot commented Sep 28, 2024

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Sep 28, 2024
@kruskall
Copy link
Member Author

@elastic/sec-linux-platform friendly ping for review

1 similar comment
@kruskall
Copy link
Member Author

@elastic/sec-linux-platform friendly ping for review

@kruskall kruskall removed the backport-8.x Automated backport to the 8.x branch with mergify label Apr 18, 2025
@mergify
Copy link
Contributor

mergify bot commented Apr 18, 2025

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @kruskall? 🙏.
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-8./d is the label to automatically backport to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@kruskall kruskall merged commit 3c89d3b into elastic:main Apr 18, 2025
1 check passed
@kruskall kruskall deleted the fix/auditbeat-filetimes branch April 18, 2025 11:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement 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