https://nf-co.re logo
Join Slack
Powered by
<@UE4L64T4G> would you have time to check why the ...
# wg-container-conversion-task-force
m
@Phil Ewels would you have time to check why the stats page is currently not building on netlify (it's on seqera, so I don't have access). can you check if there is a token called 
EVIDENCE_SOURCE__nfcore_db__token
? It should have the value from 
Motherduck Access Token
in the nf-core 1password vault
👀 1
p
Last two builds failed
Untitled
Untitled
m
yep. I can see the deploys, just a bit of a cryptic error message
I changed the @evidence/duckdb version, but I don't see why this would brake netlify. it builds fine locally
p
The 1password token looks... wrong 😅
Pretty sure it's not meant to be 
2/3/25
😁 1
But I can see the env var in netlify and it looks token-like. Similar structure and length to the "Motherstats dev token" in 1password
Then yeah, the "Motherduck Access Token" 1password item looks borked
m
Let's just try the dev token for now just to make sure it is not that
p
Changed, deploy running now..
looks good
in a "failing for other unrelated reasons" kind of way
oh it actually passed, just warnings about 
modules_container_conversion
not existing
thanks 1
lmk if / when there's a new token in 1password
👍🏻 1
m
token updated
p
Updated in Netlify salute
thanks 1
m
can you please check what the value for 
DESTINATION__MOTHERDUCK__CREDENTIALS__DATABASE
is?
p
kicked off a new build
m
should be 
nf_core_stats_bot
p
EVIDENCE_SOURCE__nfcore_db__database
is 
nf_core_stats
m
ahhh, that explains a bit. can you please update it to the bot one
p
done, kicked off a second deploy 👍🏻
thanks 1
The first one with 
nf_core_stats
worked, surprisingly
The second also worked
Both still have quite a lot of warnings about 
modules_container_conversion
not existing
Open in Slack
PreviousNext
Powered by