Can someone manually start the first release <#C08...
# aws-megatests
e
Can someone manually start the first release #C084HP11VPF AWS test please? Didn't seem to have run in https://github.com/nf-core/proteinannotator/pull/71
p
The GitHub actions has a workflow_dispatch (manual trigger)
So you should be able to do this
e
Found it!
p
Uff, that action 🫠
Is the pipeline using the latest template?
I remember @Adam Talbot and a few of us had a big effort at improving it to not give meaningless
curl
errors, but I don't remember how far we got in the end
e
It should, yea..didnt get any latest template update PRs
p
@Edmund with @Adam Talbot, me and @mashehu reviewing + doing more work on it
This action is so outdated, screenshots with "Nextflow Tower" in the readme still this is fine fire
tower 1
a
we replaced all our use of it internally with seqerakit or just straight up Python
m
👍🏻 1
a
The Javascript version of the action would be so much better but I don't feel qualified to review because I never use any Javascript.
p
We should do that on the nf-core side either way @mashehu, good catch 👍🏻
a
The action is using Tower CLI v0.12.0 and the CLI is on 0.21.0 😱
screams 3
m
homer-simpson-mirror-gif.gif
p
Let'x fix that sucka
a
Having a CLI in a Docker in an action is...a design choice
😁 3
e
Rare footage of

bioinformaticians wrapping the tw cli instead of using the API▾

😂 2
n
Any examples on how to get this working or should I just wait a bit longer?
m
I will try to work on a fix this afternoon
❤️ 1
n
Thanks! No rush here 😛
a
@mashehu if you're happy with the JS action I am!
m
breaking two nf-core backbone github actions because of JS/TS in one day... challenge accepted (the other being https://github.com/nf-core/setup-nextflow/pull/209)
p
Yeah that was another one that stalled out
r
Got a bit of time to help out with this, what's the latest?
m
a-group-of-people-are-gathered-in-a-living-room-with-a-fire-coming-out-of-the-floor.gif
did the sarek release run on aws?
r
it got submitted but failed with
Copy code
Error executing process > 'NFCORE_SAREK:PREPARE_REFERENCE_CNVKIT:CNVKIT_ANTITARGET (intervals)'

Caused by:
  Unexpected path for Fusion script launcher: /work/sarek/work-e9f175045340f34be9f273ca5a543d08ab90c661/test_full_germline_aws/b3/c476d46314e063386c2c8417926bd2
which happened in the past when the work dir that was specified didn't have the
<s3://bucket-name>
prefix
outdir is also missing it and was just specified with
/sarek/results-e9f175045340f34be9f273ca5a543d08ab90c661/test_full_germline_aws/
e
I'll fix it, but only if I can just merge cowboy until it works cowboyhat tip
r
works for me
a
@Edmund you have merge rights for the tower-action-launch so it's your problem baby now
salute 1
skedaddle
n
So is this working again? 😛
r
yes, but we should still update the tower-cli version. There have been a ton of improvements in the last 10 release 😄
n
Allright, thanks! Is this already part of the template?
e
Missed Adam's message. I'll get merging
🙌 1