Skip to content

trimfeedstart messed up feed, new data appears in future #3

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

Closed
bluehawk opened this issue Mar 8, 2018 · 0 comments · Fixed by #4
Closed

trimfeedstart messed up feed, new data appears in future #3

bluehawk opened this issue Mar 8, 2018 · 0 comments · Fixed by #4

Comments

@bluehawk
Copy link
Contributor

bluehawk commented Mar 8, 2018

I ran trimfeedstart on one of my feeds, and it worked well, it removed the old data I didn't want. Unfortunately, it seems like it messed up the feed, and now new data is being added in the future.

On Mar 7th, I trimmed the feed to start on Feb 17, removing about a month worth of messy data. That part worked, but now new data is showing up on Apr 8th, rather than Mar 8th. Note, it's not always one month of offset. I've tested other feeds, and the amount of "future offset" seems to be related to how much data was trimmed.

screen shot 2018-03-08 at 12 11 12 pm

I think I've identified the problem (not updating npoints in the feed metadata after trimming the feed), and will be submitting a fix.

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 a pull request may close this issue.

1 participant