it seems like the "aws results" tab is broken on s...
# documentation
a
it seems like the "aws results" tab is broken on several of the pipeline documentation pages? sometimes the "no aws results found" message appears as soon as i click on the tab and sometimes it takes digging into the folder structure and getting to a level where files should be
m
at least for rnaseq looks like again a hash missmatch between aws megatest run and release hash, will invistigate when i am longer in front of a computer. But maybe @Maxime Garcia can confirm this suspicion?
m
yes for rnaseq it was a missmatch on a previous release
or at least that's part of the issue
for rnavar, it's more or less pure template, and still there is the issue: https://nf-co.re/rnavar/1.1.1/results/rnavar/results-564a754458622cf4b564b2515b6a6d29160fc190/
m
And rnavar on the AWS bucket has the same directory name?
m
👀
m
for rnavar there is nothing on AWS, looks like the action failed: https://github.com/nf-core/rnavar/actions/runs/16957647684/job/48062936046#step:4:18
m
yeah, I noticed that
and I think the rnaseq action failed as well
waiting for @Edmund to wake up to ping him and investigate
e
Ah I was probably me running a test. @mashehu if I clean up the bucket will it fix the webpage?
🙌 1
m
Yes, as soon as the buckets with the right hashes are there, it will be showing them
🙌 1
e
To clarify, only the buckets with the right hashes?
👍🏻 1
Trying to wrap my head around it so we can maybe protect the bucket itself.
a
just in case it helps with prioritization, im particularly interested in the cutandrun results at the moment
e
@Alexandra Bartlett What email do you use for cloud.seqera.io? I'll just add you to the megatests workspace and you can look at them in data explorer
a
albartlett@hsph.harvard.edu. thanks so much for attending to this!
m
Yes, the hash parts are checked against the releases and only they return pages.
e
@Alexandra Bartlett shot you an invite
🙏 1