0b1414dc6d
This change avoids `RuntimeError: There is no current event loop in thread '<thread_name>'` errors when passing a resource as an input multiple times when using mocks. The problem is that when using mocks, we deserialize the gRPC inputs before passing them to the user's mock methods. Deserializing inputs doesn't typically require an event loop, however, during deserialization of resource references, we end up creating some instances of `Future`, which does require an event loop to be present for the current thread. If this is done multiple times for a resource, it's possible that `deserialize_properties` will be called on an asyncio thread that doesn't yet have an event loop, resulting in the error being raised. The error does not occur when only passing the resource reference once because typically the thread (e.g. `asyncio_0`) used in that case will have already had an event loop created for it due to the use of the internal `_syncawait` when _serializing_ the source resource's properties, which ensures an event loop is set for the thread. The fix is to ensure an event loop is created for the thread in the mocks implementation before calling `deserialize_properties`. |
||
|---|---|---|
| .. | ||
| dotnet | ||
| go | ||
| nodejs | ||
| proto | ||
| python | ||
| go.mod | ||
| go.sum | ||
| README.md | ||