-
Notifications
You must be signed in to change notification settings - Fork 9
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
KeyError: 'Time' when using pipestat via pypiper #207
Comments
One hint is this message:
It looks like there might be a bug somewhere with a constant that is getting stored as a string instead. |
I think |
actually I think it's |
I figured it out. Pypiper automatically adds results for
I think this is suboptimal, since I am not putting those in, they're automatic. Maybe pypiper should be the one adding them to the output schema, since it's the one reporting them automatically. |
I made a more informative error message in pipestat to address this here: pepkit/pipestat@0d511b5 This at least solves the immediate issue, but going forward:
|
Also confirmed this by adding the output_schema to the
It will indeed fail with a KeyError: |
When I'm trying to switch from a normal pypiper pipeline to one that configures pipestat, I'm getting this error:
I can't track this because I'm not doing anything related to
Time
. so it must be coming from pypiper or pipestat somehow.The text was updated successfully, but these errors were encountered: