Use `log` logging #13

New Issue

Closed

opened 2022-10-30 05:41:12 +00:00 by mars · 1 comment

mars commented

2022-10-30 05:41:12 +00:00

Owner

Inside of the canary, canary-sandbox, and magpie crates:

replace any and all println and eprintln calls with log logging functions
add additional logging functions for any appropriate debug data (this will be a good opportunity to learn how Canary's code flow works)
add the env_logger crate to the magpie crate for configurable logging to stdout
add egui_logger to canary-sandbox for a bottom panel with a log

Inside of the `canary`, `canary-sandbox`, and `magpie` crates: - replace any and all `println` and `eprintln` calls with `log` logging functions - add additional logging functions for any appropriate debug data (this will be a good opportunity to learn how Canary's code flow works) - add the `env_logger` crate to the `magpie` crate for configurable logging to stdout - add `egui_logger` to `canary-sandbox` for a bottom panel with a log

mars added the

feature

consistency

labels 2022-11-01 06:26:58 +00:00

mars commented

2022-11-17 06:03:35 +00:00

Author

Owner

There is a proliferation of upwards Result propogation throughout the host-side codebase. While logging is being implemented, all functions that do not depend on their caller to specially handle errors should catch and log any possible errors themselves.

There is a proliferation of upwards `Result` propogation throughout the host-side codebase. While logging is being implemented, all functions that do not depend on their caller to specially handle errors should catch and log any possible errors themselves.

mars referenced this issue

2022-11-27 04:35:36 +00:00

Magpie should delete its socket automatically on startup #19

mars referenced a pull request that will close this issue

2022-12-06 23:25:43 +00:00

Logging #53

mars closed this issue

2022-12-06 23:38:59 +00:00