some kind of retry mechanism could be useful here to make sure no events are lost
ff7801a7c1
ensure event handlers are properly subscribed on init, extract duplicated progress functions, cleanup duplication
cargo prints warnings and other stuff in stderr, meaning it can get really noisy. So we'll silence those warnings unless we're asking for debug logs (RUST_LOG=debug)
Some instrumentations are still missing, but this PR is mostly to get early feedback on the approach.
I'm not a big fan of "duplicating" all the stuff below. It is for different concerns than the ones defined in harmony_cli, but it follows the same pattern.
See the PR comment above (in examples/rust/main.rs) for more info
Ideally, this shouldn't have to be handled by the end user. But in this case, because Maestro::initialize prepares the Topology (which might execute Scores), we have to register the cli_logger early.
8fae9cf8c8
split instrumentation in 2 different places: harmony domain (for domain observability) & harmoy composer (for build/commands observability)
d95e84d6fc
Merge pull request 'fix(apps/rust): build & push using image tag instead of local VS remote image name' (#87) from fix-image-tag into master