You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when using with-duration it does not differentiate failed executions from successful ones. Since with-duration is probably around IO a failure is definitely interesting and IMO should be separated by a label (e.g. status with value success/failed - but I didn't give it much thought).
The current solution is to either write something specific (macro/manual code) or wrap twice (using with-duration and exceptions.with-exception). IMO the common use case of with-duration should consider exceptions since it is probably mostly around IO.
WDYT?
The text was updated successfully, but these errors were encountered:
Currently, when using
with-duration
it does not differentiate failed executions from successful ones. Since with-duration is probably around IO a failure is definitely interesting and IMO should be separated by a label (e.g.status
with valuesuccess
/failed
- but I didn't give it much thought).The current solution is to either write something specific (macro/manual code) or wrap twice (using
with-duration
andexceptions.with-exception
). IMO the common use case ofwith-duration
should consider exceptions since it is probably mostly around IO.WDYT?
The text was updated successfully, but these errors were encountered: