You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for await loops are intended to be used on async iterators/generators. During the development of the sync feature as a distributed loop, we noticed that the behaviour of this loops is not strictly sequential, which can lead to unexpected effects on the implementation.
As we used that approach moving the TOC job to a distributed loop, we think moving back to a reduce loop approach is the way to implement asynchronous calls inside loops.
The text was updated successfully, but these errors were encountered:
How about a plain old loop (for generators, maybe one of the whiles)? If I remember correctly, we have talked about ignoring the "no await in loop" rule in specific cases where it is needed.
for await
loops are intended to be used on async iterators/generators. During the development of the sync feature as a distributed loop, we noticed that the behaviour of this loops is not strictly sequential, which can lead to unexpected effects on the implementation.As we used that approach moving the TOC job to a distributed loop, we think moving back to a reduce loop approach is the way to implement asynchronous calls inside loops.
The text was updated successfully, but these errors were encountered: