Hi, I am new to Async and I want to know to how to resolve the following problem. I have an async.series and an array of functions are passed in as input and there is one function in that where I need to invoke async.eachOfSeries, but async.eachOfSeries gets called only once for any array.
I am assuming that async.series gets connected through invoking callback functions and same thing for async.eachOfSeries but each of these have their own callbacks to be invoked which is where I think the problem arises. ANy Ideas ?
Folks, question about using async queues - i have 2 workers each doing its own stuff, and one depends on results of other. Both workers do some heavy stuff, and if run in a loop easily overwhelm the system. I hoped to run these workers in 2 queues, limiting the number of simultaneously executed workers. The task submitted to one queue once accomplished would push the second task to second queue, and both would execute its tasks in parallel. However, it has appeared that second queue wouldn't start execution of its tasks until first queue was done doing its own tasks. Why is that? Is it intended by design, or I'm missing something?
Here my code in the gist https://gist.github.com/abuzarhamza/03724d121f41bd410ba45a7bbbf97bff .. I have seen some time few people use
currying to pass callback , Is it a good practice or should I use call?
I'm wondering if there's some kind of serialization method where a series of async.js calls can be serialized into a particular format - like JSON, for instance.
Not sure if my question there makes sense, apologies!
I have something like this
fetch(...)
.then((results) => {
let list = ...
async.mapLimit(list, async (item) => ... );
return ... ?
/// ???
});
Async doesn't return promises, can I use promisify?
If I want to build the dist from source, how would I do that?
I didn't see any instructions in the readme
I've been using the library for a while now and I love it. It's incredibly elegant. But when I tried to use it within an app.get, it didn't wait for each function in the series to finish. It just moved on to the next one in the series and completely blew up my sequence. Thoughts?
Hello, how do I use async.queue in a sequential manner?
I've read that for a static array of tasks, sequential execution can be achieved through async.series, if one requires push/pop, one should use queue instead. I've set up my queue as
const RequestQueue = queue(() => {}, 1);but the 2nd item (a fetch request) always executes before the 1st item (also a fetch request) finishes.
Sample Task:
retrieveConnectionsTask = () => {
RequestWrapper.get("/myEndpoint")
.then(response =>
response.json()
)
.then(data => {
//doSomethingWithData
console.log("retrieveConnectionsTask Returned");
console.dir(this.state.connections);
})
.catch(error => console.log(error));
};would appreciate any advice.
Thank you!
Hello everyone.
You might be interested by an open-source project I recently started which is basically a rewrite of Async.js but aimed for exclusive usage of async/await and promises.
The code is here: https://github.com/nicolas-van/modern-async
I would welcome any comment.
I also have been working on a replacement for some (but not all) parts of
async. Mine is iter-tools, and it only focuses on iterables, but I think it has significant advantages. It ensures resources are released (by calling iterator.return() if it is present), it has a better approach to parallelization, and it offers more performant implementations of methods over sync iterators. In 8.0 I plan to change my methods around a bit so that import { asyncMap } from 'iter-tools' beceomes import { map } from 'iter-tools/async', which I think will be more familiar to users of this library.
Hey guys, I'm working on a pr to work around some of the throttling issues with
setImmediate which becomes setTimeout in the browser. I'm having a hard time building the lib for testing though, even from a vanilla repo. What I've done:- Checkout the repo
- install deps
- run
make
That results in the following:
make: *** No rule to make target `build/all.js', needed by `build-modules'. Stop.
I didn't see a
contributing guide or anything like that, am I missing some setup steps?
Is there a tutorial on how to use async queue correctly? I seem to have abused the error callback to trigger tasks :D
or since @nicolas-van you are promoting your lib, can you give me an example for an async queue :D
or maybe I better say what i'm trying to do, maybe queue is the wrong thing. I want to fire async api calls but to not DDoS the DB I want to fire only some at a time and queue the rest for after those have finished
and I also want to merge the results of the api calls
what exactly is a
task btw? is it just meta info about a task or is it a function that is executed?
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/74b1c6f746407578fce1e44b25215a3bde4f9a3e/types/async/index.d.ts#L28
This callback type looks like it should return a promise but it doesn't.
This callback type looks like it should return a promise but it doesn't.
Oh dear, I see. This was originally callback-based async, and promise support was added to the library but seemingly not the typedefs. Also the promise support seems super janky, for some reason the docs say that you can't use promise-returning functions as callbacks, only actual async functions. See: https://caolan.github.io/async/v3/index.js.html#line1
Here, i am using async simply because the syntax is clearer than promise.all