Configuration tab on run page resolving to `n/a` when specifying `enabled = true` in `~/.nextflow/config`

[James A. Fellows Yates]

I've identified an issue that the resolved configuration section of the 'configuration' tab of runs are reported as just n/a when I activate enabled = true in the tower scope of (any) nextflow config file. It doesn't happen when I run with -with-tower.

This happens both sending to my personal workspace as well as an organisation workspace. I have tested this both with NXF_VER 21.10.6 and 21.04.3

i.e. in ~/.nextflow/config (note screenshots taken from 21.04.3 as latest tested, but also apply to 21.10.6)

tower {
  enabled = true
  accessToken = '<YOUR TOKEN>'
  workspaceId = '<YOUR WORKSPACE ID>'
}

nextflow run nf-core/eager -profile test

will result in n/a

but

tower {
  accessToken = '<YOUR TOKEN>'
  workspaceId = '<YOUR WORKSPACE ID>'
}

nextflow run nf-core/eager -profile test -with-tower

works OK and I see the resolved configuration.

[Abhinav Sharma]

Thanks for letting us know @jfy133, we've already initiated a PR to address it nextflow-io/nextflow#2642

As soon as next nf-tower plugin version is out, it should be fixed for all recent NF releases.

[James A. Fellows Yates]

Awesome thanks!