Currently, Bazel generates three different build configurations for the underlying FFI library during C# driver deployment. As that requires compilation of the binding generator and lengthy project analysis, that step is prone to random failures (socket closed).
As the full analysis of the issue proved time-consuming, we instead opt to make the C# driver deployment step easily retriable.
Usage and product changes
Currently, Bazel generates three different build configurations for the underlying FFI library during C# driver deployment. As that requires compilation of the binding generator and lengthy project analysis, that step is prone to random failures (
socket closed).As the full analysis of the issue proved time-consuming, we instead opt to make the C# driver deployment step easily retriable.