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

Propagate Sync error when running SafeFileRotate #9069

Merged
merged 2 commits into from
Nov 15, 2018

Conversation

kvch
Copy link
Contributor

@kvch kvch commented Nov 14, 2018

Previously, it was possible SafeFileRotate encountered an error without propagating it, because the return value of os.Sync was not utilized.
From now on the errors from Sync are propagated.

Copy link
Member

@ruflin ruflin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add a changelog entry?

@kvch
Copy link
Contributor Author

kvch commented Nov 15, 2018

@ruflin Done.

@kvch kvch merged commit 93eb92a into elastic:master Nov 15, 2018
@ph ph added the needs_backport PR is waiting to be backported to other branches. label Nov 15, 2018
@ph
Copy link
Contributor

ph commented Nov 15, 2018

@kvch I have added the needs_backport, My understand is we want to use that to debug maybe an issue so I think we should port it to 6.x, 6.5.

kvch added a commit to kvch/beats that referenced this pull request Nov 19, 2018
Previously, it was possible SafeFileRotate encountered an error without propagating it, because the return value of os.Sync was not utilized.
From now on the errors from Sync are propagated.
(cherry picked from commit 93eb92a)
@kvch kvch added v6.6.0 and removed needs_backport PR is waiting to be backported to other branches. labels Nov 19, 2018
kvch added a commit to kvch/beats that referenced this pull request Nov 19, 2018
Previously, it was possible SafeFileRotate encountered an error without propagating it, because the return value of os.Sync was not utilized.
From now on the errors from Sync are propagated.
(cherry picked from commit 93eb92a)
@kvch kvch added the v6.5.1 label Nov 19, 2018
kvch added a commit that referenced this pull request Nov 21, 2018
…otate (#9142)

* Propagate Sync error when running SafeFileRotate (#9069)

Previously, it was possible SafeFileRotate encountered an error without propagating it, because the return value of os.Sync was not utilized.
From now on the errors from Sync are propagated.
(cherry picked from commit 93eb92a)
kvch added a commit that referenced this pull request Nov 22, 2018
…otate (#9141)

* Propagate Sync error when running SafeFileRotate (#9069)

Previously, it was possible SafeFileRotate encountered an error without propagating it, because the return value of os.Sync was not utilized.
From now on the errors from Sync are propagated.
(cherry picked from commit 93eb92a)
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…feFileRotate (elastic#9142)

* Propagate Sync error when running SafeFileRotate (elastic#9069)

Previously, it was possible SafeFileRotate encountered an error without propagating it, because the return value of os.Sync was not utilized.
From now on the errors from Sync are propagated.
(cherry picked from commit 84bdbd9)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants