Closed aspett closed 4 years ago
@aspett Hey :wave:, thank you for using Sage. Indeed they should be fixed and I'll push a release shortly, there is nothing you need to do about that 👍
Sage 0.6 is out, please try it and tell if there is something wrong. Thank you again 🎊
Hey @AndrewDryga thank you so much for that! I've updated it in one codebase, and so far so good. I noticed the removal of the {failed_stage, reason}
argument in compensations which is a bit of a shame. We were using that in a couple of places to basically only retry if it failed on the same stage as the compensation was associated with. I think there will be ways to refactor how we do this though.
@aspett I see your use case. I think we should do something different to support it, mainly because if we pass other stage names to compensations we tell people that compensation can have complex logic when it's better to push for their pure design. Maybe we can add some API to the Sage itself to only accept retry
command if an error occurred on the same stage.
Hiya @AndrewDryga - we're using Sage quite a lot and have recently upgraded to elixir 1.10. We've noticed a lot of warnings on
0.4.0
, and I'd forked with the intention of cleaning them up and pull requesting, but I see that they're all actually fixed on master. Keen to understand your appetite for a 0.5.0 or 1.0.0 release (appears there are some breaking API changes), and if there's anything I can do to help get there?