https://nf-co.re logo
Join Slack
Powered by
The CI in <#CJRH30T6V> uses the latest dev from <#...
# infrastructure
m
The CI in #CJRH30T6V uses the latest dev from #CE5LG7WMB, but the linting is broken because that enforces 
meta_containers
. What’s the recommended action?
m
what is --fix doing if you try the command?
m
well, nothing 🤷🏻 since I’m not running the dev version locally
As I assume most users are, which is the issue here
n
You can use codespaces to get an env where it is installed, i've also had some issues with 
--fix
though (see #CE5LG7WMB)
m
yeah, was just going to say 
nf-core modules lint riker/multi --fix
doesn’t do anything, even on dev
m
I always have latest dev on modules, and the tools that match the pipeline I am working on
n
Pinging @mashehu here 😛
e
I'm also watching :p
👋 2
👋🏻 1
m
..... must... not.... force merge....
🤣 1
n
shared a GIF
m
sweat
n
(if that's the only failure I'd say that it's fine to force merge)
m
Let’s not abuse priveliges and try to fix the issue at it’s (nf-)core first 😉
➕ 1
n
I agree in 99% of the cases, but this has no impact on the downstream pipelines as none of them are already using the new container system 😛 But eh it's fine if you can wait of course
m
PR with fix is incoming
❤️ 4
m
I knew Matthias would come and save the day
deal with infra 1
m
well, I was the one that broke it...
m
You are cleaning after, that's still good behavior, so thank you
n
That was probably an inevitability given the size of that change 😛
m
should be fixed now (including the incorrect 
--fix
@Nicolas Vannieuwkerke got for expansionhunter's meta.yml
🙌 1
n
That's awesome! I'll give it a go in one of my following PRs 😛
2 Views
Open in Slack
PreviousNext
Powered by