Matthias Zepper
03/07/2025, 5:28 PMtw CLI (tw launch --profile).
I think the problem is, that the centralized configs are now added with a conditional includeConfig that Seqera platform can no longer correctly resolve includeConfig !System.getenv('NXF_OFFLINE') && params.custom_config_base .
Any test helps, but particularly those people with access to Platform and using local offline pipelines on a HPC via an agent would be relevant here. 🙏James Fellows Yates
03/08/2025, 9:37 AMpontus
03/08/2025, 1:04 PMJames Fellows Yates
03/08/2025, 1:05 PMMatthias Zepper
03/08/2025, 1:24 PMnextflow.config inside the pipeline repository. So I can't launch a pipeline with the uppmax profile for example, because it will tell me, that I selected an invalid profile.pontus
03/08/2025, 3:24 PMMatthias Zepper
03/08/2025, 6:09 PMnextflow config on that, to determine the available profiles. But if you change the revision or commit in the GUI, that must be rerun and the same applies, when you manually enter additional config in the GUI.
Regardless what exactly that communication looks like, the ultimate config is pieced together on Platform as an ephemeral single file, so it might not be able to evaluate System.getenv() correctly.