Skip to content

Conversation

@sgran
Copy link

@sgran sgran commented Dec 11, 2014

For some reason, I'm seeing timestamp, value tuples of (None, None)
consistently as the last item in the list on returns from cyanite. Skip
bad timestamps defensively.

Signed-off-by: Stephen Gran steve@lobefin.net

For some reason, I'm seeing timestamp, value tuples of (None, None)
consistently as the last item in the list on returns from cyanite.  Skip
bad timestamps defensively.

Signed-off-by: Stephen Gran <steve@lobefin.net>
@brutasse
Copy link
Owner

@sgran thanks! That looks like something that should be fixed in cyanite directly… We'll have a look with @pyr.

@sgran
Copy link
Author

sgran commented Dec 12, 2014

yeah, that might be a good idea as well - I'm not sure why cyanite is returning (None, None) for the last array element, but it seems like a useful guard anyway. Up to you, though :)

Cheers,

@brutasse
Copy link
Owner

@sgran there might be some misalignment between the (start, end, step) info and the number of datapoints passed (see zip_longest above your change). Do you still see this regularly? Can you try with the new cyanite (requires schema change)?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants