Closed tfenne closed 1 year ago
That's unusual. Can you post/share the code of the TRIM_ADAPTERS
task?
Unable to replicate. Closing this.
We've seen this again in a different client's (private) workflow.
A complete shot in the dark, but werhaps we need the following somewhere:
kryo.setReferences(true)
kryo.setRegistrationRequired(false)
This will be really hard to reproduce and provide a test case, but we'll continue looking for one.
Bug report
Expected behavior and actual behavior
Recently a workflow I've been working with for months has started having (apparently) spurious problems with using cached tasks. E.g. I'll have a run of the workflow that got almost to the end, then hit a bug in a new task. I'll make a tiny change to my
main.nf
and re-run, and then a whole bunch of tasks fail to resume from cache.To me it seems random. E.g. in a workflow with 4 samples, 3/4 "TRIM_ADAPTERS" tasks will fail to resume, but the 1/4 will resume just fine. Same happens with other processes.
My log is full of stack traces like this:
I have no idea what the
25
refers to in theEncountered unregistered class ID: 25
.Steps to reproduce the problem
Program output
Environment
Additional context