Fix nested async loop #143
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes the asyncio error:
RuntimeError: asyncio.run() cannot be called from a running event loop
This situation occurs when someone does something stupid. For example, runs synchronous code in asynchronous code, which runs asynchronous code from yascheduler through synchronous code.
For example, when a WSGI netius server runs a synchronous flask app that tries to add a task to the yascheduler via a synchronous wrapper.
The point of the fix is to make a neater wrapper that runs asynchronous code in a thread pool. Also, asynchronous methods are made available for use. These are used in cli utils.
Other changes to fix CI: