Closed vivecalindahlericsson closed 3 years ago
Hi, I'm a bot from the Ray team :)
To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.
If there is no further activity in the 14 days, the issue will be closed!
You can always ask for help on our discussion forum or Ray's public slack channel.
Hi again! The issue will be closed because there has been no more activity in the 14 days since the last message.
Please feel free to reopen or open a new issue if you'd still like it to be addressed.
Again, you can always ask for help on our discussion forum or Ray's public slack channel.
Thanks again for opening the issue!
When running Impala with a busy scheduling of new simulations (short horizon, many resets), I got the following assertion error
After a significant amount of checking code, trial and error debugging, I realized that the source of the problems is a queue-related timeout that should lead to an error (I think) but for some reason the assertion error is what is seen. There is also a trainer config parameter for the timeout
"learner_queue_timeout": 300
.It would be helpful to catch the timeout earlier and provide a more helpful error message, e.g. pointing to the timeout parameter.