-
Notifications
You must be signed in to change notification settings - Fork 2
pipestat retrieval breaks with common prefix #159
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
Comments
Additional info: Confirmed it is just for the filebackend. |
Found it: should be
I'm failing a couple of tests with this change so I need to investigate that. |
This is fixed |
Can you add in a test that mimics the above? Like, have two samples named |
Might be good to see if this solves pepkit/looper#470 (which should probably move to pipestat) |
Yes, I already added that test |
I can confirm the fix is working correctly in my hands, thanks. |
If I have two record identifiers that share a common prefix, pipestat will return the value for the shorter one even when you request the longer one.
This may be the root of this problem I found earlier in looper: pepkit/looper#470
Watch this:
Create pipestatmanager object
Here's my
seqcol_pipestat_schema.yaml
Report/retrieve results is broken if you use similar sample names:
And continuing:
It seems that if anything matches the first prefix of the sample, it will return that somehow. This is a critical bug.
The problem is with retrieval, not with reporting, because the file itself is actually correct, it shows:
The text was updated successfully, but these errors were encountered: