You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
As a newcomer to this package, I'm exploring the usage of the AsyncRunner feature, particularly aiming to employ the start_periodical_saving functionality. Below is the code snippet I've implemented:
Since the AsyncRunner doesn't work well in a script environment, I ran it in a jupyternotebook using the %run magic command, and got the error message pointing to runner.ioloop.run_until_complete(runner.task)
RuntimeError: Thiseventloopisalreadyrunning
I suspect that the conflict arises because the runner.start_periodic_saving coroutine initiates its own event loop, which contradicts the use of run_until_complete function. Since run_until_complete is crucial for me as it ensures sequential execution of subsequent functions after runner.task completion, I'm seeking guidance on resolving this issue.
Request for Assistance:
Could you provide guidance on how to address this conflict and enable the sequential execution of functions following runner.task completion, given the necessity of using run_until_complete?
Apology for encountering another issue within such a short timeframe. Your package is truly remarkable and has significantly contributed to the success of my project. Thanks for your kind assistance
The text was updated successfully, but these errors were encountered:
Oops. I just find a sad fact that AsyncRunner won't work for me since I'm using HDF5 library to save my data which doesn't support asyncio. h5py issue#837
Thus my problem turns out to be: will it be possible to add learner.save() feature in the BlockingRunnner class? It is necessarily supported by the asyncio feature?
The save method does actually not need to be an async method itself. It just needs to be a normal function of type Callable[[LearnerType], None].
So for example
defsave(learner):
learner.save(**save_kwargs)
Regarding your async problems, in a script you can block with: runner.ioloop.run_until_complete(runner.task), however, in a notebook you can simply do await runner.task (docs).
Description:
As a newcomer to this package, I'm exploring the usage of the
AsyncRunner
feature, particularly aiming to employ thestart_periodical_saving
functionality. Below is the code snippet I've implemented:Since the
AsyncRunner
doesn't work well in a script environment, I ran it in a jupyternotebook using the%run
magic command, and got the error message pointing torunner.ioloop.run_until_complete(runner.task)
I suspect that the conflict arises because the
runner.start_periodic_saving
coroutine initiates its own event loop, which contradicts the use ofrun_until_complete
function. Sincerun_until_complete
is crucial for me as it ensures sequential execution of subsequent functions afterrunner.task completion
, I'm seeking guidance on resolving this issue.Request for Assistance:
Could you provide guidance on how to address this conflict and enable the sequential execution of functions following
runner.task
completion, given the necessity of usingrun_until_complete
?Apology for encountering another issue within such a short timeframe. Your package is truly remarkable and has significantly contributed to the success of my project. Thanks for your kind assistance
The text was updated successfully, but these errors were encountered: