Add job list page

[superstar54]

To help users easily search and manage their jobs, this PR adds a new job list page. This is the first step to fix #515 .

Home page

On the home page, I added a new Utils section on the right side of the logo. Currently, there is only the job list item, but we can add more items in the future, e.g., 'plugin list' in #646 .

Job list page

• show a table of the processes: pk, ctime, state, relaxed, properties
• delete button and inspect button.

Demo

qeapp-joblist.mp4

Future improvement

After this PR, open issues on

• add search bar

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.47%. Comparing base (f63da7d) to head (6e57bc5).
Report is 58 commits behind head on main.

❗ Current head 6e57bc5 differs from pull request most recent head 402faa4. Consider uploading reports for the commit 402faa4 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #657      +/-   ##
==========================================
- Coverage   80.73%   75.47%   -5.26%     
==========================================
  Files          49       60      +11     
  Lines        3415     4404     +989     
==========================================
+ Hits         2757     3324     +567     
- Misses        658     1080     +422     

Flag	Coverage Δ
python-3.10	75.47% <ø> (-5.26%)	⬇️
python-3.8	?
python-3.9	75.50% <ø> (-5.27%)	⬇️

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.

[AndresOrtegaGuerrero]

@superstar54 Nice, I will test it and let you know, I was wondering. If an user has a WorkChain , maybe lets say a bands , but the structure as an input is coming from another WorkChain, and by deleting the first node it deletes automatically all the linked nodes. Is this avoided?

[superstar54]

If an user has a WorkChain , maybe lets say a bands , but the structure as an input is coming from another WorkChain, and by deleting the first node it deletes automatically all the linked nodes. Is this avoided?

Good question. I will look into it and provide more information to the user when deleting nodes.

[AndresOrtegaGuerrero]

@superstar54 I really like the job list, is easy to search through jobs. I could be nice if there is a choice to add some filters like, filter by state : Finished[0] , or properties. I guess in this page the search app from edan could be useful.

[AndresOrtegaGuerrero]

@superstar54 I would suggest you add a section explaning that by deleting a node (QeWorkChain) all the associated and link nodes will be eliminated , as well as other calculations that might be linked with this node.

[AndresOrtegaGuerrero]

Also It might be a good idea to display the number nodes associated, so the person know what nodes or workchains are being deleted

[superstar54]

Yes, I display the number of nodes to be deleted.

[superstar54]

I really like the job list, is easy to search through jobs. I could be nice if there is a choice to add some filters like, filter by state : Finished[0] , or properties. I guess in this page the search app from edan could be useful.

Thanks, I added basic search filters. We can use @edan-bainglass 's query builder when it's ready in the future.

[superstar54]

from @cpignedoli and @giovannipizzi

• Add label/description for search.
• allow edit the label/description.

Add extras for the properties

[superstar54]

Not delete a job, but hide it.

[superstar54]

Hi @AndresOrtegaGuerrero , I made the changes as you suggested. Here is the screenshot of the page when user deleting a node. Could you please have another look?

[AndresOrtegaGuerrero]

<font color="red"><b>Caution!</b></font> Deleting this job will also remove <b>all associated nodes</b>, including any workflows that share a common input structure, as well as various calculations and their respective results. <b>This action is irreversible.</b>

[superstar54]

Hi Andres, thanks for the comment.

including any workflows that share a common input structure

It will not delete the workflows that share the input structure. It only deletes its descendants.

• If QEApp jobs A and B use the same input structure, if A is deleted, B will not.
• If QEApp job A has an output structure and job B uses it as input, then if A is deleted, B will also be deleted. I added a check here; in this case, the user can not delete job A.

[AndresOrtegaGuerrero]

Hey Xing , it looks good to me , just check the few typos. I was wondering something, is it possible to check if the selected node to deete has other QeAppWorkChain associated ? and display this ? if not we can leave it for a future PR

[superstar54]

Hi @AndresOrtegaGuerrero , thanks for the review and suggestion. I have implemented the changes as you suggested.

I was wondering something, is it possible to check if the selected node to deete has other QeAppWorkChain associated ? and display this ? if not we can leave it for a future PR

Yes, it's possible. I have added a check to see if there is a QEApp job using the outputs of the nodes that need to be deleted. If there is, the deletion will be blocked. Only after the user deletes the related QEApp job can the root one be deleted.

[AndresOrtegaGuerrero]

LGTM!