We encountered the following synchronization problem while using .each(). We couldn't figure out if it is intentionally design like this or a bug based on the documentation, so would like to get any insight from you guys:
It's definitely a bug, the reduce implementation in 2.x is notoriously complicated and each delegates to it as well hence it is affected. The implementation has been redone in 3.x and it shouldn't have this bug. If this is critical for you I can make a patch for 2.9.13.
Thanks for getting back super fast. Right now we are using a work around by chaining a .then() as a pass through to make it really async. It would be awesome if we can have a patch release soon. Also, when are you planning for the 3.x release?