refactor(journaldriver): Use anyhow instead of failure
Apparently failure is not hip anymore, and crate updates are forcing the use of anyhow now. Whatever. The functionality basically stays the same, maybe error messages will look a little bit different now. Change-Id: I173d644688785339c16161ddeec47a534123710f Reviewed-on: https://cl.tvl.fyi/c/depot/+/5307 Tested-by: BuildkiteCI Reviewed-by: sterni <sternenseemann@systemli.org> Autosubmit: tazjin <tazjin@tvl.su>
This commit is contained in:
parent
4ce2b49cd9
commit
ede837b687
3 changed files with 240 additions and 312 deletions
|
|
@ -5,9 +5,9 @@ authors = ["Vincent Ambo <mail@tazj.in>"]
|
|||
license = "GPL-3.0-or-later"
|
||||
|
||||
[dependencies]
|
||||
anyhow = "1.0"
|
||||
chrono = { version = "0.4", features = [ "serde" ]}
|
||||
env_logger = "0.5"
|
||||
failure = "0.1"
|
||||
lazy_static = "1.0"
|
||||
log = "0.4"
|
||||
medallion = "2.2"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue