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.

Sign up for GitHub

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

Jump to bottom

Refgenconf should give a more specific error when an non-existing asset is queried #139

Open
nsheff opened this issue Jul 7, 2022 · 2 comments
Open

Refgenconf should give a more specific error when an non-existing asset is queried #139

nsheff opened this issue Jul 7, 2022 · 2 comments
Assignees
@rafalstepien

Comments

@nsheff
Copy link
Contributor

nsheff commented Jul 7, 2022

See: databio/pepatac#216 (comment)

If an asset is missing, it should be more specific than "TypeError: 'NoneType' object is not iterable"
@nsheff nsheff changed the title Refgenconf should give a more specfiic error when an non-existing asset is queried Refgenconf should give a more specific error when an non-existing asset is queried Jul 7, 2022
@nsheff
Copy link
Contributor Author

nsheff commented Jul 7, 2022

Update refgenconf so instead of "TypeError: 'NoneType' object is not iterable" at that line, we actually specify the seek_key_name that is being specified.

@rafalstepien rafalstepien self-assigned this Jul 7, 2022
@rafalstepien
Copy link

#140

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rafalstepien rafalstepien

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nsheff @rafalstepien