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
journaldriver: 1.0.0 -> 1.1.0 #48106
Conversation
Included changes: * upstream repository has moved, URLs changed accordingly * journaldriver bumped to new upstream release The new release includes an important workaround for an issue that could cause log-forwarding to fail after service restarts due to invalid journal cursors being persisted.
Update: |
@GrahamcOfBorg build journaldriver |
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: journaldriver Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: journaldriver Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: journaldriver Partial log (click to expand)
|
Included changes: * upstream repository has moved, URLs changed accordingly * journaldriver bumped to new upstream release The new release includes an important workaround for an issue that could cause log-forwarding to fail after service restarts due to invalid journal cursors being persisted. (cherry picked from commit 5ead273) backported because of moved upstream repo
backported in 18.09 because of moved upstream repo: 59fe4c7 |
Thanks a ton @xeji! |
Motivation for this change
The new release includes an important workaround/fix for an issue that could cause log-forwarding to fail after service restarts due to invalid journal cursors being persisted.
Journaldriver was included in 18.09 - is it possible to get this version bump backported for that fix?
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)