-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Looking for a way to not exit on async.parallel on error. #675
Comments
We can call it |
Or perhaps a different route. Instead of a whole new function, we could just wrap the individual functions in a
or
|
There's a whole bunch of async combinators you could write to more easily plug functions together. I like this one, for when you don't care about the error. Another one would be to make async functions plug into the |
Also, not sure about "surge" -- the theme isn't really electrical. |
Good feed back, thanks @aearly. You don't think this should be included with async? |
I'd wait to see what other think. There's a lot of stuff that could go in the grab-bag that is async. |
Having this as part of async would be great. |
I'm putting together a collection of auxilliary higher-order async helper functions: acomb. A function like this would be welcome if you want to make a PR. :) |
@aearly Took a look at acomb, really neat! |
+1, would love to see an option to continue on errors, too (although I don't need it for |
+1 for continuing on errors. |
+1 |
5 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
How to continue *parallel* processing in case of a failing task seems to be a frequently asked question. It was mentioned in several issues: - caolan/async#334 - caolan/async#675 - caolan/async#798 - caolan/async#942 Adding a hint to the documentation might help users of the library to find out about the answer to this question.
Majority of my most recent use-cases involve async functions that aren't dependent on each other, and so when some async function breaks up top, the rest of my code doesn't execute. Wondering if there's a simple way to do something like this without being so obtrusive to the library / so much overhead. In this case I'd like to return false on error, so I'm building an object with every property intact, if something fails everything is else is still there, and false takes the broken async functions place.
@aearly Would love your thoughts on this one too.
The text was updated successfully, but these errors were encountered: