Dan Caseley
Dan Caseley
Feel free to create one, and I'll merge em if I find it.
> (I'm sure there's a ticket in here somewhere about exposing success/error state on the maestro object in JS) I meant a ticket on the issue tracker. I don't believe...
My feeling is that this hook would be useful, but... In the situation where you've got multiple teardown steps, you might also need the flow result, because of specific ordering...
I think redefining this as "having failure status automatically available in the onFlowComplete hook" would seem like an appropriate solution to this?
When you say "we", you're referring to the enormous collective that can contribute to open source, right? From individuals with a passion, to companies who can have the software they...
Shards was implemented specifically to deal with this. I _think_ there's an open issue around somewhere about port detection / collision, where there was a suggestion about Maestro being able...
@omnarayan Useful: Linking this issue from the PR so that when the PR is resolved this issue can be closed. Not useful: tagging me everywhere, complaining about your lack of...
@ff-vivek Have you been able to get any feedback on this yet?
Just waiting on some engineering capacity to get it reviewed. I've had a play with it, and it all LGTM, but I wanted a second set of eyes before hitting...
Are you able to provide the hierarchy? You should find it in ~/.maestro/logs, or you can run `maestro hierarchy` when the test fails