Because the ganga tab looks like the other tabs in SWAN (projects, cernbox and sharing), they should all behave the same.
You already import the tree/main.min.js but not everything works. If you click "..." and then in "Running processes", nothing happens.
To fix this, add the corresponding html elements of the tree.html OR merge your part into the tree.html and use some ifs.

When logging again the running Condor jobs should be automatically picked up by the monitoring and completed eventually.

Add this button on the right hand side. It should show/hide all job widgets in the notebook.

Logfile for monitoring: ~/.ganga-monitoring.log

Hint: set the location of this logfile close the where you run: ganga.runMonitoring()

Ref:

You should import * from ganga into the namespace of the magic cell.

User needs to be able to write:

%%ganga
j=Job()
j.backend=Condor()
j.submit()

It would be good to quickly access the Ganga Jobs tab from the notebook page.

For example, a button that opens a new tab could be added in the toolbar on the right:

When job is submitted there is a considerable delay between the widget appears.

What is blocking and causing this delay?

If job is not found to be defined in the %ganga cell then only error should be printed.

Currently it also gives a long traceback:

swan-qa-004:

I set Condor() backend but this was lost (and reset to default which is Local()):

There is dead code that needs to be removed or code needs to be simplified.

For example:

https://github.com/apsknight/gangaextension/blob/master/extension/gangaextension/kernelextension/gangajob.py#L176

And all other cases.

Currently it will fail more complex job constructor:

Also you need to document current limitations, for example this code will not detect the job:

This is also for this repo: https://github.com/apsknight/ganga

Add environment variable to enable all your customizations: GANGA_SWAN_INTEGRATION.
Make sure your extension sets this variable.

If this variable is not defined then ganga behaviour should not be modified.

When done issue a pull request to Ganga upstream.

Tested on swan-qa004 (with previously created job). I don't know how to reproduce it.

When job is accessed there is an exception: Incorrect index cache of 'jobs' object #4 was corrected!

This error disappeared after a while -- maybe the job was reloaded from disk?

Exception:

There are very few comments currently.

The first job I submitted (j.submit() in another cell!) stays in the submitted state in the widget.

The second job (submitted later) has completed (so the first one should be completed too).

On the monitoring page both are completed:

Missing Features:

• Implement Job Cancellation button.
• Add Job Duration time column in Job Info.
• Implement resubmit button for failed/killed jobs.
• Add individual subjob info/status collapsible menu below job info row.

Known Bugs:

• Handle execution of magic cell before kernel starts.
• Create new thread for Ganga to avoid interruption of kernel.
• Improve code quality and refactor Kernel and Cell Monitor code.
• Filter out unnecessary CSS.

Widgets not cleared (also check other menu actions)

This may be triggered by #6 but not only. Sometimes it happens "randomly".

This is 100% reproducible.

Requires Ganga update to be deployed @diocas

This happens where there is no kerberos ticket.

Problem 1: unhandled exception
Problem 2: it will likely cause the subsequent cell to hang forever

Correct behaviour should be: error message to the user, job not submitted (in new state).

Please check if you get the same problem with unhandled exception on Ganga without your modification.



Please add architecture diagram (draw.io) which shows how Ganga and Notebook components (threads, processes) interact with each other in a SWAN session.

I submitted several jobs one after the other in the same cell.

The I opened the Jobs tab and I noticed that one of my jobs has REMOVE status (but it was submitted).

Could this be some race condition with widget/ganga communication if the same cell is re-evaluated to early and new job crated?

Access to the ~/.ganga-monitoring.log file: add a hyperlink here but not editable (view mode)

Rename the "Ganga Jobs" to "Jobs"

Design choice is: one job per cell only. It needs documentation.

If more jobs detected in the cell then give a warning to the user: “Only displaying the first job” or alike.