-
Notifications
You must be signed in to change notification settings - Fork 5
2022.2 #68
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
2022.2 #68
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@antgonza Just one comment.
qp_qiime2/__init__.py
Outdated
# As of qiime2-2022.2 nothing is filtered here, so let's raise | ||
# an error so we can catch and review if this happens in the | ||
# future | ||
raise ValueError(f"[REVIEW] {pname} {mid} due to {ename}") | ||
add_method = False |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you raise ValueError here, add_method will never be set to False. Is this desired?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, if this happens we want everything to stop and have someone look - cause it should never happen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
duh! Now, now I understand what you mean ... yes.
Right, but you have a statement that can never be reached afterwards. Would you mind removing it, please? Thank you!
… On Jun 3, 2022, at 11:12 AM, Antonio Gonzalez ***@***.***> wrote:
@antgonza commented on this pull request.
In qp_qiime2/__init__.py:
> @@ -155,6 +172,10 @@
# this is an odd one, first encountered:
# feature-classifier fit-classifier-naive-bayes
if ename == element.NOVALUE:
+ # As of qiime2-2022.2 nothing is filtered here, so let's raise
+ # an error so we can catch and review if this happens in the
+ # future
+ raise ValueError(f"[REVIEW] {pname} {mid} due to {ename}")
add_method = False
yes, if this happens we want everything to stop and have someone look - cause it should never happen.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because your review was requested.
|
Updating to 2022.2