GitLab

* db_version/73:
  [ENSCORESW-3372] remove copyright notice from guiHive interface
  copyright update 2020

* db_version/62:
  [ENSCORESW-3372] remove copyright notice from guiHive interface
  copyright update 2020

* db_version/73:
  Remove recursive buildURL call that was causing a multiple parameter update bug
  allow PASSED_ON jobs to be viewed in the jobs table, and allow jobs to be updated to PASSED_ON status
  remove deprecated async : false
  change after updating select list value, this seems to fix the problem of UI crash after multiple unlisted value updates
  update buildURL and update_db to properly work asynchronously when users input custom values

* db_version/62:
  Remove recursive buildURL call that was causing a multiple parameter update bug
  allow PASSED_ON jobs to be viewed in the jobs table, and allow jobs to be updated to PASSED_ON status
  remove deprecated async : false
  change after updating select list value, this seems to fix the problem of UI crash after multiple unlisted value updates
  update buildURL and update_db to properly work asynchronously when users input custom values

allow PASSED_ON jobs to be viewed in the jobs table, and allow jobs to be updated to PASSED_ON status

change after updating select list value, this seems to fix the problem of UI crash after multiple unlisted value updates

* db_version/73:
  Updated css for display fix

* db_version/62:
  Updated css for display fix

update db_fetch_max_retry_count.pl to deal with change in version_check::check_db_versions_match() return type

* db_version/73:
  job table information box added, and interactive elements now respond to single instead of double click

* db_version/62:
  job table information box added, and interactive elements now respond to single instead of double click

* db_version/56:
  job table information box added, and interactive elements now respond to single instead of double click

job table information box added, and interactive elements now respond to single instead of double click

AnalysisData entries can be shared between jobs, so we can't delete them without checking if they're still used

At the moment, I can't think of a way of checking that without a
transaction / a locking mechanism, which could be slow in large databases
(cf hoover_pipeline.pl which doesn not hoover the analysis_data table for
the same reason).
Since I don't expect many input_ids to be changed this way, I think we can
accept keeping the old entries.

lib/version_check.pm is not the best place, but it is loaded in every
script, and I didn't want to create a new module with just one function.

This means that the purple blobs that represent conditional dataflows are
not put on top of the outgoing connections, and we can finally see which
condition goes to which analysis.

* db_version/73:
  Some versions of GraphViz transform the colour names to hexadecimal

* db_version/62:
  Some versions of GraphViz transform the colour names to hexadecimal

* db_version/56:
  Some versions of GraphViz transform the colour names to hexadecimal

* db_version/73:
  Let the user know if graphviz has failed (even though we can't capture stderr)

* db_version/62:
  Let the user know if graphviz has failed (even though we can't capture stderr)

* db_version/56:
  Let the user know if graphviz has failed (even though we can't capture stderr)