-
Notifications
You must be signed in to change notification settings - Fork 594
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
barclay fails to set collection arguments initialized with an immutable collection #4702
Comments
For @cmnbroad |
There's a solution here: broadinstitute/barclay#102 |
Also, some discussion about what to do with immutable collections in barclay is here: broadinstitute/barclay#100 |
cwhelan
pushed a commit
to cwhelan/gatk-linked-reads
that referenced
this issue
May 25, 2018
…ist arguments (broadinstitute#4703) Barclay can't currently handle immutable collections in @argument values due to broadinstitute#4702 Tests for these arguments are coming in a separate, larger branch, but I wanted to get the fixes in first since it's such a simple fix.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you have a barclay
@Argument
field of typeList
, barclay will fail to set the field value properly when the argument is specified if theList
is initialized using an immutable Collection, such as that returned byCollections.emptyList()
. Example error:Ideally, barclay should detect immutable collections and replace them with mutable ones when necessary.
The text was updated successfully, but these errors were encountered: