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

Field is not valid: CommentedSeq expected null or string #1673

Open
jjkoehorst opened this issue May 30, 2022 · 3 comments
Open

Field is not valid: CommentedSeq expected null or string #1673

jjkoehorst opened this issue May 30, 2022 · 3 comments

Comments

@jjkoehorst
Copy link

Expected Behavior

When providing a YAML with a list variable to an entry that requires an optional string should throw an error stating that a list was provided and that a null or string was expected.

Actual Behavior

It complains about a CommentedSeq value while its actually a list.

QUALITY.yaml:7:1: the `kraken_database` field is not valid 
because value is a CommentedSeq, expected null or string

Workflow Code

  kraken_database:
    type: string?
    label: Kraken2 database
    doc: Kraken2 database location
    default: "/unlock/references/databases/Kraken2/K2_PlusPF_20210517"

Your Environment

  • cwltool version: INFO /usr/local/bin/cwltool 3.1.20220520101121
@mr-c
Copy link
Member

mr-c commented May 30, 2022

Thanks @jjkoehorst ; I agree this error message could be improved; Here CommentedSeq is a commented sequence, so it was referring to a list, just not in a helpful way.

@jjkoehorst
Copy link
Author

Ah I was already wondering why it was detecting sequences as in DNA / Sequencing data...

@ElderMedic
Copy link
Collaborator

This error message is very obscure, also took me some time to troubleshoot, please consider improving. Thanks!

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

3 participants