Ouch, this looks bad / high priority: <https://git...
# websitep
Phil Ewels
07/22/2026, 8:00 AMOuch, this looks bad / high priority: https://github.com/nf-core/website/issues/4317
Got Claude looking now but @mashehu if you could put eyes on it too please..
Phil Ewels
07/22/2026, 8:01 AMDuplicate issue: https://github.com/nf-core/website/issues/3462
Phil Ewels
07/22/2026, 8:02 AMOh but that one is from nearly a year ago?
Phil Ewels
07/22/2026, 8:03 AMAh I think it's ok now: https://nf-co.re/nextflow_version
Phil Ewels
07/22/2026, 8:03 AMSo presumably was a build glitch?
m
mashehu
07/22/2026, 8:04 AMyeah, difficult to debug, but also saw it tonight in tools CI. edmund put out a setup-nextflow release, which might have fixed it, but haven't had enough time to look into it.
p
Phil Ewels
07/22/2026, 8:15 AMquick look 1
Phil Ewels
07/22/2026, 8:15 AMYeah I think the solution is to just catch the glitch
Phil Ewels
07/22/2026, 8:16 AMWe wrapped the fetch in a try / catch instead of propagating the error. The above removes that.
Phil Ewels
07/22/2026, 8:16 AMStops the build and means we don't publish an empty JSON
Phil Ewels
07/22/2026, 8:16 AMEdmund's release is complementary - but it didn't cover all use I think so we need both.
👍🏻 1
2 Views