deinstapel / cursive-flexi-logger-view Goto Github PK

Log messages containing newlines are printed like this: (using the termion backend)

line1
     line2
          line3

I fixed the issue myself (WIP: FliegendeWurst@b2a84f6) and will open a PR soon.

After I start the application I got the error below and how it looks in the app

mintozzy@laptop:~/tmp/storytel-tui$ cargo run
Finished dev [unoptimized + debuginfo] target(s) in 0.50s
Running target/debug/storytel-tui
[flexi_logger][ERRCODE::Time] flexi_logger has to work with UTC rather than with local time, caused by IndeterminateOffset
See https://docs.rs/flexi_logger/latest/flexi_logger/error_info/index.html#time
[flexi_logger][ERRCODE::Write] writing log line failed, caused by Custom { kind: BrokenPipe, error: "cursive callback sink is closed!" }
See https://docs.rs/flexi_logger/latest/flexi_logger/error_info/index.html#write

[dependencies]
reqwest = { version = "0.11.11", features = ["json", "blocking"] }
serde = { version = "1.0.139", features = ["derive"] }
serde_json = "1.0.82"
mpv = "0.2.3"
openssl = { version = "0.10.41" }
cursive = { version = "0.18" , default-features = false, features = ["crossterm-backend"]}
cursive-flexi-logger-view = "^0"
flexi_logger = "0.22.6"

I used the example code https://docs.rs/cursive-flexi-logger-view/latest/cursive_flexi_logger_view/#using-the-flexiloggerview

what can be the reason ?

feel free to check https://stackoverflow.com/questions/75200289/cursive-flexi-logger-view-throwing-unhandled-error too.

Thanks

As part of the update to 0.15 cursive has migrated their logic (and by that the parts we actually need for this crate) to cursive_core. We should move to use this new crate, for now it requires us to move our end2end tests out of /src into /examples as proposed in our other view crates proposed.

As mentioned in deinstapel/cursive-tabs#5 we can make this work, but the cleaner way to handle the tests is switching to cursive::backends:puppet in all end2end tests.

It would be great if the logger-view could use the format that was set on the flexi logger instance. If this is not possible, some other way to override the default styling would be nice.

After updating to latest flexi_logger 0.28.0 I started getting the following error:1

error[E0277]: the trait bound `CursiveLogWriter: LogWriter` is not satisfied
   --> src/bin/main.rs:180:13
    |
180 |             cursive_flexi_logger_view::cursive_flexi_logger(&cursive)
    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `LogWriter` is not implemented for `CursiveLogWriter`
    |
    = help: the trait `LogWriter` is implemented for `FileLogWriter`
    = note: required for the cast from `Box<CursiveLogWriter>` to `Box<(dyn LogWriter + 'static)>`

cargo tree output:

├── cursive-flexi-logger-view v0.5.0
...
│   ├── cursive_core v0.3.7 (*)
│   ├── flexi_logger v0.22.5

It seems that cursive-flexi-logger-view is pulling in flexi_logger that doesn't match the version I wish to use?