-
Notifications
You must be signed in to change notification settings - Fork 11
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
Make IO errors paintful explicit in logrotate generator #1022
Merged
blt
merged 1 commit into
main
from
blt/make_io_errors_paintful_explicit_in_logrotate_generator
Oct 3, 2024
Merged
Make IO errors paintful explicit in logrotate generator #1022
blt
merged 1 commit into
main
from
blt/make_io_errors_paintful_explicit_in_logrotate_generator
Oct 3, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 2, 2024
blt
force-pushed
the
blt/add_error_logs_around_logrotate_errors
branch
from
October 2, 2024 21:03
4cf9d85
to
11a7f62
Compare
blt
force-pushed
the
blt/make_io_errors_paintful_explicit_in_logrotate_generator
branch
from
October 2, 2024 21:03
10fe605
to
d57289e
Compare
goxberry
approved these changes
Oct 2, 2024
blt
force-pushed
the
blt/add_error_logs_around_logrotate_errors
branch
from
October 3, 2024 00:07
11a7f62
to
32ddd92
Compare
blt
force-pushed
the
blt/make_io_errors_paintful_explicit_in_logrotate_generator
branch
from
October 3, 2024 00:08
d57289e
to
dd09a2f
Compare
blt
force-pushed
the
blt/add_error_logs_around_logrotate_errors
branch
from
October 3, 2024 00:39
32ddd92
to
29d14af
Compare
blt
force-pushed
the
blt/make_io_errors_paintful_explicit_in_logrotate_generator
branch
from
October 3, 2024 00:40
dd09a2f
to
fb34d2e
Compare
blt
force-pushed
the
blt/add_error_logs_around_logrotate_errors
branch
from
October 3, 2024 01:13
29d14af
to
f821f6d
Compare
blt
force-pushed
the
blt/make_io_errors_paintful_explicit_in_logrotate_generator
branch
from
October 3, 2024 01:14
fb34d2e
to
687ad7b
Compare
blt
force-pushed
the
blt/add_error_logs_around_logrotate_errors
branch
from
October 3, 2024 01:49
f821f6d
to
1d07073
Compare
blt
force-pushed
the
blt/make_io_errors_paintful_explicit_in_logrotate_generator
branch
from
October 3, 2024 01:50
687ad7b
to
f9255a3
Compare
blt
force-pushed
the
blt/add_error_logs_around_logrotate_errors
branch
from
October 3, 2024 02:26
1d07073
to
0f42af8
Compare
blt
force-pushed
the
blt/make_io_errors_paintful_explicit_in_logrotate_generator
branch
from
October 3, 2024 02:26
f9255a3
to
a1669f9
Compare
blt
force-pushed
the
blt/add_error_logs_around_logrotate_errors
branch
2 times, most recently
from
October 3, 2024 03:01
8bf5399
to
76513c6
Compare
blt
force-pushed
the
blt/make_io_errors_paintful_explicit_in_logrotate_generator
branch
from
October 3, 2024 03:01
a1669f9
to
5deb7c7
Compare
blt
changed the base branch from
blt/add_error_logs_around_logrotate_errors
to
graphite-base/1022
October 3, 2024 03:34
blt
force-pushed
the
graphite-base/1022
branch
from
October 3, 2024 03:34
76513c6
to
ec1eaf5
Compare
blt
force-pushed
the
blt/make_io_errors_paintful_explicit_in_logrotate_generator
branch
from
October 3, 2024 03:34
5deb7c7
to
c3f1183
Compare
In my downstack PR I discovered that in fact we have some IO error happening in practice although exactly which one who can say. This PR attempts to say. I've gone through and made every error very explicit and where possible added the paths being acted on. Signed-off-by: Brian L. Troutwine <[email protected]>
blt
force-pushed
the
blt/make_io_errors_paintful_explicit_in_logrotate_generator
branch
from
October 3, 2024 03:35
c3f1183
to
d2f74d9
Compare
blt
deleted the
blt/make_io_errors_paintful_explicit_in_logrotate_generator
branch
October 3, 2024 04:11
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
In my downstack PR I discovered that in fact we have some IO error happening
in practice although exactly which one who can say. This PR attempts to say.
I've gone through and made every error very explicit and where possible added
the paths being acted on.