Invalid Mermaid DAG with nested workflows

[kdesnos]

Bug report

Expected behavior and actual behavior

When using nested hierarchical workflow with more than 2 levels of hierarchy, in case where a workflow is instantiated several times below the first level of hierarchy, without any aliasing of the workflow name, the exported DAG with mermaid does not reflect the nextflow dag.

Steps to reproduce the problem

Consider the following MWE, where the sub_sub workflow is instantiated twice by two different sub_x workflows in the top level workflow.

process a {

    output:
        stdout

    script: 
    """
        echo "I'm a process"
    """
}

workflow sub_sub {
    a()
}

workflow sub_2 {
    sub_sub()
}

workflow sub_1 {
    sub_sub()
}

workflow {
    sub_1()
    sub_2()
}

Program output

The exported mermaid graph has the following code:

flowchart TB
    subgraph sub_1
    subgraph sub_sub
    v0([a])
    end
    end
    subgraph " "
    v1["-"]
    v3["-"]
    end
    subgraph sub_2
    subgraph sub_sub
    v2([a])
    end
    end
    v0 --> v1
    v2 --> v3

Which seems fine on paper. Unfortunately, mermaid can have a unique subgraph with name sub_sub, and as a result, when displaying the graph, two instances of a are displayed within sub_1::sub_sub, while the subgraph of sub_2 remains empty.

Environment

• Nextflow version: 24.10.4
• Java version: openjdk 11.0.20 2023-07-18
• Operating system: Linux
  • Bash version: GNU bash, version 5.1.8(1)-release (x86_64-redhat-linux-gnu)