Open delarosatrevin opened 7 months ago
I think it is cached . But I. This case it can't even cache it. We shoul tolerate errors there.
El jue., 7 dic. 2023 21:13, Jose Miguel de la Rosa Trevin < @.***> escribió:
Assigned #486 https://github.com/scipion-em/scipion-pyworkflow/issues/486 to @pconesa https://github.com/pconesa.
— Reply to this email directly, view it on GitHub https://github.com/scipion-em/scipion-pyworkflow/issues/486#event-11186420436, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAF7ZYJABZTSQ5PJ2H6O4T3YIIPOBAVCNFSM6AAAAABALUETGSVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGE4DMNBSGA2DGNQ . You are receiving this because you were assigned.Message ID: @.*** com>
Apart from being cached, might be a good idea to do the updated in a background thread. This will prevent blocking the GUI, even in the case where the size needs to be re-calculated.
In running protocols where some tmp folders/files are deleted, it can raise the following exception:
Moreover, for some large datasets (e.g. tens of thousands of movies) this can take a long time to compute and freeze the whole GUI.
I propose to either avoid that computation or have some sort of cache value that prevents from running that many IO queries every time one hover over a protocol box.