Allow to continue after failure
See original GitHub issueAsync APIs calls to their callback function as soon as there’s a failure. I propose to add an option to do just the oposite: if there’s an error, continue with the other tasks until they finish, and only in that moment call to the callback with the error (or errors). This can be useful for example with parallel
to finish all the tasks instead of left some of them unfinished.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5
Top Results From Across the Web
Why should someone try continue, after failure? - Quora
Failure tells you your weaknesses and by overcoming them you will become strong as well as experienced person in your work. Your dedication...
Read more >Why Do Some People Succeed after Failing, While Others ...
Evans of the University of Chicago, Wang found that success comes down to learning from one's prior mistakes—for instance, continuing to improve ...
Read more >10 Healthy Ways to Cope With Failure - Verywell Mind
Once you've identified your mistakes and where you can learn from them, you'll be ready to make a plan for moving forward. Remember...
Read more >Continue on fail option - IBM
For each item in the test suite, enable (select) or disable (clear) the Continue on Fail option according to how the suite is...
Read more >How do I Continue After a Failure in SSIS
To answer the question as I asked it, it is possible to continue after failures by making sure that MaximumErrorCount is zero for...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Have you also seen
reflect
/reflectAll
? They make every async task complete successfully, and wraps the result down to a{error, result}
object you can then inspect.I think this use case is well-handled by
reflect
/reflectAll
.