Tim de Jager fc0f637406 Make the BuildDispatch interpreter method async (#14956) ... This is a bit of a weird request, but in [pixi](https://pixi.sh) we are making use of this function to lazily instantiate a conda environment. Well, in actuality we are using a shim to the `BuildDispatch` to actually to only create a conda prefix, if some package needs to be built during the resolution phase. Otherwise we can resolve everything without an enviroment containing a python intepreter. We are using a method now - that uses the runtime to run async code inside this function, as `interpreter` is the first method called on a `BuildContext` when running a source build - using `tokio::Handle::block_on`. However was causing a deadlock in very specific situations, me and @baszalmstra + @wolfv have investigated this thoroughly, but have not been able to find the root cause. It would hang in a part of the uv code that hits the index, but that is **after** all of our initialization *and the blocking call* was completed. Changing this to be fully async fixes the problem, this requires this method to be async though. We get that this is not necessarily required, and we might find a workaround, but I wanted to try it this way first. Thanks!		2025-07-31 06:42:27 -05:00
..
src	Make the BuildDispatch interpreter method async (#14956)	2025-07-31 06:42:27 -05:00
Cargo.toml	Cache workspace discovery (#12096)	2025-03-10 22:03:30 +01:00