1.208

It is possible to define custom signals for remote submit jobs and their child stages. This might be useful when there are different possibilities for stopping a job.

For example, this provides the possibility to define a custom STOP signal for a particular stage. When triggered, the STOP signal would end the corresponding stage gracefully and still execute the following stages. Whereas a KILL signal could forcefully stop the corresponding stage and cancel all subsequent stages for that remote assembly.

Prerequisites: Runner version 0.26.1.

In order to better understand the recurring performance problems experienced by users, a sampling profiler is available in the client. In case of slow actions in the client, users can start a profiler and record that action. The record, which is a DAT file, can be sent to the developers for analysis. This feature is currently available only for the Linux client.

Pool versions which are available online (remote pool versions) but not downloaded for local users are now also displayed in the pool version selection view and also in the filter view. The remote pool versions are identifiable with the cloud icon enclosing the status of the pool version. This feature is currently not activated by default and should be activated explicitly using the features=show_remote_pool_versions start option.

This feature is still in development.

The properties view has a new category called Run outputs. It displays:

• for assembled runs, the available run output components for a multi-stage assembly.

  

• details of the assembled run from which run output component is imported.

  

• Attachment names are now shown without prefixes.
• Tool tips are available for long names.
• Attachments uploaded as ISO-MME data are now grouped as per ISO-MME structure.

Since the pool UUID is unique and permanent, the check mechanism should only check the UUID and not the name which can be changed. This eliminates problems in mounting a pool after it has been renamed.