Hello- as we continue to ramp up on Seqera Cloud, ...
# seqera-platform-community-help
k
Hello- as we continue to ramp up on Seqera Cloud, is there somewhere to find a list of issues and possible workarounds? I'm tripping over an uncaught
Copy code
at nextflow.cloud.google.secrets.GoogleSecretsProvider.getSecret(GoogleSecretsProvider.groovy:131)
šŸ‘€ 1
For the curious, more details are here: github.com/broadinstitute/nf-send-mail-example#… Since I can't find the source code for
GoogleSecretsProvider
, I suppose one could always submit a patch to nextflow to add a try/catch around this line: github.com/nextflow-io/nextflow/blob/…/SecretsLoader.groovy#…
p
For Seqera Cloud, there is some functionality in Nextflow that comes from non-OSS plugins. If you can't find the source code, it's entirely possible that the traceback is coming from there.
For these, the options are: • Contact support (will definitely get a response and hopefully a fix) • Post on community.seqera.io (better for this kind of thing than slack, as posts with relevant tags get auto-posted into the Seqera slack šŸ‘€ 🤫 ) • Post here, as you did šŸ™‚ (in which case I usually poke people to respond).
Also contacting support does not have to be mutually exclusive: if you're a Seqera customer then I would basically always recommend doing this. Our support team are awesome, and it's one of the main benefits of being a customer šŸ™‚
seqera party 1
r
@Khalid Shakir Hi! I'm from Seqera support, and we've just sent you a reply back on the ticket you've submitted re: the above issue. I've confirmed there is a bug in the Google secrets provider, and the fix for that lives in a Seqera-maintained plugin codebase. I've included more details in your Support Ticket, and happy to help answer questions in the meantime!
gratitude thank you 2