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
When using concurrency features like ThreadPoolExecutor's map function as well as un-ordered collections like sets to spawn off several dynamic requests, it's sometimes impossible to force the requests to always occur in the same order as when the cassette was recorded. In order to account for this, it would be great if there was a way to ignore request ordering when matching cassettes.
The text was updated successfully, but these errors were encountered:
When using concurrency features like
ThreadPoolExecutor
'smap
function as well as un-ordered collections likeset
s to spawn off several dynamic requests, it's sometimes impossible to force the requests to always occur in the same order as when the cassette was recorded. In order to account for this, it would be great if there was a way to ignore request ordering when matching cassettes.The text was updated successfully, but these errors were encountered: