Trigger the update of node view

[superstar54]

This PR fixes the process monitor to update the result tabs.

The ideal solution is: as long as the process is updated (e.g., has a new output), we trigger the update of the node view. However this is not possible in the current ProcessMonitor. Therefore, we only trigger the update when the process is finished.

I opened an issue on the ProcessMonitor.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.35%. Comparing base (6101655) to head (df837ea).
Report is 88 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #844      +/-   ##
==========================================
+ Coverage   68.32%   68.35%   +0.03%     
==========================================
  Files          50       50              
  Lines        4568     4573       +5     
==========================================
+ Hits         3121     3126       +5     
  Misses       1447     1447              

Flag	Coverage Δ
python-3.11	68.35% <100.00%> (+0.03%)	⬆️
python-3.9	68.38% <100.00%> (+0.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[superstar54]

Here is an example to show the result tabs are automatically generated when the process is finished. Please go to ~ 30 seconds of the vedio.

qeapp-update-result-tabs.mp4

[AndresOrtegaGuerrero]

How this timeout works ?, Could it lead to any memory issue for a workflow that takes long ?

[superstar54]

For the moment, the ProcessMonitor will call the callback functions every timeout seconds. This, indeed, will be a problem if the callback function is computationally expensive.

In principle, we only need to run the callback function when the process is finished (or even better, when the process is modified). I have opened an issue in the aiidalab-widget-base.

We can wait for that issue to be solved before merging this PR.

[AndresOrtegaGuerrero]

or at least we should increase the time , 1 second is to often

[superstar54]

We use a small value for the timeout, so that the results can be immediately shown when the process is finished.

As pointed out by @danielhollas , there is a on_sealed argument for the callbacks. I changed the callback to on_sealed, so that the _update_view method will only call when the process is finished. In this case, the timeout 1 s should be fine.

[AndresOrtegaGuerrero]

LGTM! thank you Xing