GitLab

There are now two methods to get the name of an object
 - display_name() returns the name of the object in its own local context
 - relative_display_name() returns the name of the object in the given
   context. If the object is local to the given pipeline, this is the same
   as display_name()

relative_display_name() is implemented in Cacheable. display_name() has a
default implementation in Cacheable too, but is often overloaded in the
sub-classes

new Analysis::get_grouped_dataflow_rules used by print_diagram/print_diagram_node called from generate_graph.pl

seed_pipeline is now HivePipeline-aware, can find analysis by a pattern and calls HP::get_source_analyses

Make sure the Runnable dies if it did not receive all the expected data (instead of producing an incorrect result)

It is no longer necessary, because adding the Analyses is actually not symmetrical:
collections of the "native" pipeline know about the newly added objects,
but these objects still refer to their "foreign" hive_pipeline, which makes it possible
to derive their original AnalysisStats dynamically.
Keep this in mind until adding these objects is no longer necessary (desired redesign plan).

* version/2.3:
  Don't need %hash_interval, can simply use %hash_curr_workers
  bugfix: make sure the plot start exactly at $start_date
  Decreased the threshold for detecting rounding errors. This allows to show memory usage as low as 5Mb
  bugfix: alive workers are now displayed until the current time

* version/2.2:
  Don't need %hash_interval, can simply use %hash_curr_workers
  bugfix: make sure the plot start exactly at $start_date
  Decreased the threshold for detecting rounding errors. This allows to show memory usage as low as 5Mb
  bugfix: alive workers are now displayed until the current time

cherry picked from commit master - bcd6efd7 and bugfixed
again to correctly initialize the first data-point