Open MohammadMahdiJavid opened 9 months ago
since self.status_queue is empty, so again it's going to say
if (time.time() - self._last_status_received) > STATUS_TIMEOUT:
and is going to use previous self._last_status_received for the new one and raise the exception again
proposed fix:
if self.status_queue.empty() :
self.status_queue.put(0)
or maybe i'm handling the exception not correctly
RuntimeError: No status update from the storage controller process for 4859 seconds.
This implies that the following code has not been running for more than an hour, which is deeply troubling as it should run every 5 seconds.
This suggests that you are performing long running blocking operations in the storage controller which breaks it. The storage process is a single threaded asynchronous execution environment. Any task (including any storage provider) that doesn't yield control can lock up the whole process.
I would assume that whatever is blocking the process is also preventing any data from getting saved out.
This can not be fixed anywhere outside of the storage (controller) process
Hi,
I am encountering a specific RuntimeError when using OpenWPM and I am seeking advice on the correct approach to handle it. The error occurs as follows:
I attempted to handle this exception with a try-except block, but it doesn't seem to be effective:
I would appreciate any guidance on the correct way to handle this exception. Is there a specific approach or pattern recommended for handling such timeouts or lack of status updates in OpenWPM? Any insights or suggestions would be greatly appreciated.
Thank you.
https://github.com/openwpm/OpenWPM/blob/25c537eb8eb8ac1e7b7f399ba5830bb37859332d/openwpm/task_manager.py#L410-L429
https://github.com/openwpm/OpenWPM/blob/25c537eb8eb8ac1e7b7f399ba5830bb37859332d/openwpm/storage/storage_controller.py#L536-L555