Closed BioWilko closed 2 years ago
Asklepian failed after an attempted re-raise, the pipe appears to be failing at this part of the script.
Some absolute carnage sequences in here today. I've let @rmcolq know there may be issues downstream.
I think the plan of action is:
fasta_quickcheck
process in elan.nf
because this was embarrassinghttps://github.com/SamStudio8/majora/commit/916c5d4c3d4559c74456ed85e2833c4a4b575260 will allow select users to remove absolute garbage from the data set without approval from the uploading institute
directly assigned can_suppress_any_pags_via_api
to @BioWilko who can now mark the 171 affected records in Majora
All affected records suppressed.
confirmed
(samstudio8) [nicholsz@bham control]$ ocarina --oauth --quiet --env get pag --mode pagfiles --test-name 'cog-uk-elan-minimal-qc' --pass --suppressed-after 2022-01-05 --task-wait --task-wait-attempts 15 --task-wait-minutes 1 | grep -c consensus
[WAIT] Giving Majora a minute to finish task fcc75b12-81ca-40d7-918d-cbf9c8870a67 (1)...
[WAIT] Finished waiting with status SUCCESS (1)...
171
Manually running cog-publish.sh now to force refresh today's data set
We've never re-run the publish script on the same day like this before so needed a few new tricks:
Looking promising:
[DONE] 1848739 hits, 0 misses, 0 skips, 171 kills
Removing Asklep 20220105 guards
@BioWilko can you raise
Raised
gofasta
is streaming an MSA now so we're out of the woods and back to normal service :rocket:
Pulled @BioWilko's patch (https://github.com/SamStudio8/elan-nextflow/commit/4828e44e50d4859d8612d06e03e69ca30c1b2dc9) that will ensure the fasta_quickcheck
step will boot out spurious garbage like this in future, conveniently also putting #38 to rest for good too.
MSA is finished and we're proceeding with the genome and variant tables as normal now. That's enough hot sauce for one day, nice work @BioWilko. Call me if anything else blows up!
This issue has had knock on effects, follow this issue for more information.
Close but no cigar on this one. I should have noticed this yesterday:
We've never re-run the publish script on the same day like this before so needed a few new tricks:
- Updated publish script to run on empty add (as all new files had been processed earlier already there was nothing new to do) SamStudio8/elan-nextflow@1db3637
There should have been new work to do because we were publishing OVER the newly published data.
Brief description
[Provide a sentence of background]
Pipeline exit code: 1
Executed by: @BioWilko BIRM
[ ] Set appropriate issue flags and assignee
[ ] Manual intervention complete
"Normal" service disrupted? YES/NO
If yes, describe impact: