-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fixed Supported ctTSO LabMetadata sample Type Assay combo #514
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.
Great work!
This will exclude a specific type/assay combination, but the GH issue mentions to exclude all but the known/supported ones? Why the "If UNSUPPORTED then fail" instead of "if not SUPPORTED then fail"? Sorry, I may be missing some context here. |
Eh. El. Ok. Think, I got wut you mean. You mean other samples type and assay combo? I would not consider those yet. That would be pretty broad meta evaluation that might need done elsewhere... I think. May be, at SampleSheet Checker? I think, I might write the GH issue description a bit vague. My aim is being specific and, fail-safe switch here. Such that this ctTSO annotation combo is well-known and, the most hotspot failure/confusion point. So want to eliminate that. |
I know and I agree that this will eliminate this known issue case. All I am saying is: are we keeping the door open for other cases where we could easily close it? In this case here, I don't know. |
Sure. Happy to close as much as possible, of course. Think, we need to discuss these other cases... yes.
That's correct. It was and, is still permissive! |
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.
For the current case it looks OK.
(don't what to stall over improvements)
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.
(Ok, updated GH issue tickie to reflect specific to ctTSO case.)
Baby step, Flo! Baby step. 👶 We will get there, sure. 😉 And... towards OrcaBus! 🐳
Yeah I think allowlist is probably a better way to control than a blocklist. But probably need to think about this further. |
Fixed #508