`AutoProvider` coroutine bug
- Dominant language
- Python
- Stars
- 5.5k
- Forks
- 1.7k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 2
Description
### What happened?
reported by @fubuloubu
### Fill this section in if you know how this could or should be fixed
The `AutoProvider` needs async support. We should write a test that runs through each provider class we have and makes sure that we can connect appropriately and that it disconnects with cleanup.
We should write up the `WebSocketProvider` as the default websocket provider and expect that this is asynchronous. This is a breaking change since it would replace the `LegacyWebsocketProvider` so it should probably stay behind a flag for now with a warning that the websocket provider will be asynchronous in `v8` once the `LegacyWebscoketProvider` is removed.
This usage should also be documented in our docs.
Contributor guide
Assessment
This issue has not been assessed yet.