Handle logging and errors between rust and flutter.

[akhudek]

I'm looking for some help in handling logging and fatal errors between rust and flutter. For one, I've seen some packages that try to send any log::info etc messages to the flutter logging system. Are any compatible with rinf?

Second, I'd like to be able to handle fatal errors on the rust side more easily. E.g. it would be good to surface unexpected panics and send them to a crash reporter or debug log that users can send over rather than have a silent failure.

I suppose I could try to build something like this myself via a stream and panic intercept, but is there an already established way?

[temeddix]

Hi @akhudek , thanks for leaving your opinion :) Sorry for being late here, because I've been busy with daily things.

If you set successful value of RustResponse as false, it should indicate that the Rust side failed to do something that was requested from the Dart side. I do wonder when this way of handling errors might not be sufficient.

[akhudek]

Thanks for the response, and yes I do use that for errors that I expect might happen and that can be handled. What I'm trying to find a way to handle are errors that are unexpected and that you think should never happen. E.g. maybe a hardware failure breaks initialization, or a resource file somehow goes missing or is corrupted.

In these situations there is no real way to recover from the error, and I don't even know what error to check for. In my particular app I have at the top level of some calls an foo.expect("foo") because I want to panic the app at this point and report the issue.

Extending this to rinf, I would ideally want the panic bubbled to the flutter side so that I could handle it with a crash reporting mechanism. Currently this is bubbled to flutter only as a console print. Adding a flutter side callback hook to handle panics would be helpful.

On the logging side, I'm currently logging information to the windows event trancing framework from rust, and the default logging on the flutter side. Maybe getting. both going to event tracing would good enough. The main use for logging that I envision would be help in debugging in the case where an error is only happing on a users computer.

[temeddix]

I will focus in adding support for returning Rust errors soon, thanks for your opinion :) maybe it would be done using something like Rust's catch_unwind