Skip to content
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.

Sign up for GitHub

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

Jump to bottom

async.parallel - allowing all functions to finish even if error is thrown #798

Closed
ORESoftware opened this issue Jun 19, 2015 · 2 comments
Closed

async.parallel - allowing all functions to finish even if error is thrown #798

ORESoftware opened this issue Jun 19, 2015 · 2 comments
Labels
duplicate feature

Comments

@ORESoftware
Copy link
Contributor

Hello, thanks for your wonderful lib !!

One question I have - is it possible to pass async.parallel a parameter to tell it to not immediately call the final callback when there is an error passed callback(err,null) by one of the parallel functions?

I want to be able to put all the errors in an array + I also want to allow all the functions to complete, even in the case of an error in one or more of them.

Does this make sense? is it already possible?
@aearly
Copy link
Collaborator

aearly commented Jun 20, 2015

Very similar to #531 and #675. We're still deciding on the best way to do this, and what the API should look like...

@aearly aearly closed this as completed Jun 20, 2015
@ORESoftware
Copy link
Contributor Author

all you need is optional boolean as first arg!!

:)

that's my thinking after thinking about it for 3 seconds

@PierreFritsch PierreFritsch mentioned this issue Mar 16, 2017
Merged
ipyramiddev added a commit to ipyramiddev/async-300 that referenced this issue Dec 10, 2022
@ipyramiddev
Add a hint to reflect in the documentation of parallel
ed2c551 
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aearly @ORESoftware