the dynamic spawn strategy is broken for remote execution #8646
We have received several bug reports about the dynamic spawn strategy not working properly with remote execution / caching. I took some time to look through the code to better understand the issue. I believe to now understand the heart of the issue.
The dynamic spawn strategy in a single line:
This line takes the result of the first callable to finish and calls
This has two issues:
I believe 2.) is what users are most likely to see.