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
That NameError caused each operation to fail, but because join_successes discarded the failures, one_two_three succeeded. I had error logging on an errback, but it never got logged, which left me scratching my head for a while.
In a context where the constituent deferrables are expected to succeed, it would be nicer for the join combinator to immediately escalate any failure. Something like this:
# If any of the joined deferrables fails, fails immediately with that failure's error.# Otherwise waits for all deferrables to succeed, and succeeds with an array of success results.classJoinCarefully < DeferrableGratification::Combinators::Joinprivatedefdone?failures.length > 0 || all_completed?enddeffinishiffailures.empty?succeed(successes)elsefail(failures.first)endendend
The text was updated successfully, but these errors were encountered:
I spent a while trying to track down a bug that was masked by
DG::join_successes
. What happened was something like this:That NameError caused each
operation
to fail, but becausejoin_successes
discarded the failures,one_two_three
succeeded. I had error logging on an errback, but it never got logged, which left me scratching my head for a while.In a context where the constituent deferrables are expected to succeed, it would be nicer for the join combinator to immediately escalate any failure. Something like this:
The text was updated successfully, but these errors were encountered: