Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: AttributeError Exception when running workflow that includes a tool that consumes a collection #2806

Closed
lparsons opened this issue Aug 17, 2016 · 12 comments

Comments

@lparsons
Copy link
Contributor

lparsons commented Aug 17, 2016

Running this workflow consistently generates an exception.

Workflow: https://gist.github.com/lparsons/22c019a295ede562ee8583e44718170a

Exception: https://gist.github.com/lparsons/6962086d8a8c02d46b3857d8b0ad0441

AttributeError: 'HistoryDatasetAssociation' object has no attribute 'dataset_instance'

@lparsons lparsons changed the title BUG: Exception when running workflow that includes a tool that consumes a collection BUG: AttributeError Exception when running workflow that includes a tool that consumes a collection Aug 17, 2016
@lparsons
Copy link
Contributor Author

lparsons commented Sep 2, 2016

Unfortunately, I'm still seeing this on version 16.07. Is there anything I can do to help troubleshoot for this?

@jmchilton
Copy link
Member

It is nearly impossible to visualize these JSON files - can you post a screenshot also?

@jmchilton
Copy link
Member

Does that last step with the input:

<param name="inputs" type="data" label="Input .bam File(s)" format="bam" help="(--input-file)" multiple="true"/>

Have a single dataset or a list of datasets going into it?

@lparsons
Copy link
Contributor Author

lparsons commented Sep 2, 2016

Sure, here's a link to screenshot: http://i.imgur.com/rlKm0k8.png

Not sure which step you're referring to...

@lparsons
Copy link
Contributor Author

lparsons commented Sep 2, 2016

Ahhh... Yes, that's the XML from the genebody_coverage.xml tool. Yes, that has a list going into it.

@jmchilton
Copy link
Member

@lparsons - can you try cloning the workflow, deleting that step and running the result workflow?

@lparsons
Copy link
Contributor Author

lparsons commented Sep 2, 2016

@jmchilton - sure, I did that and it ran without issue.

@jmchilton
Copy link
Member

Does that tool run on the outputs on its own now (outside a workflow) - it looks like this is a exception in the exception handling is why I ask?

@lparsons
Copy link
Contributor Author

lparsons commented Sep 2, 2016

Yes, it runs find on a list outside of a workflow. (and yes, on those same outputs).

@jmchilton
Copy link
Member

Did this happen prior to 16.07 also?

I'd guess something is getting double wrapped with these Galaxy wrapper objects, if that is the case the following patch may help https://gist.github.com/jmchilton/5cba0e67744f02148dcb16d5dc3f2743.

@lparsons
Copy link
Contributor Author

lparsons commented Sep 2, 2016

Yes, this happened on 16.04 as well (not sure about before that). I'll try out the patch and see what happens.

@lparsons
Copy link
Contributor Author

lparsons commented Sep 2, 2016

@jmchilton - that seemed to fix it... Though now I get a proxy error due to a timeout issue (takes too long to create all the jobs, but they get created.

martenson added a commit that referenced this issue Sep 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants