Skip to content
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

Events imported from Meetup have bad future dates #118

Open
kentonh opened this issue Oct 8, 2017 · 2 comments
Open

Events imported from Meetup have bad future dates #118

kentonh opened this issue Oct 8, 2017 · 2 comments

Comments

@kentonh
Copy link
Member

kentonh commented Oct 8, 2017

@sethetter The importer scheduled a few (10 or so) events with ending dates in the year 4000.
I'm not sure if it's a consistent issue or not, but it's work a check

@sethetter
Copy link
Member

@kentonh have you corrected the dates? If so, can you point me to which ones (at least one) that had a crazy future date like that?

@sethetter
Copy link
Member

Looking at lib/tasks/pull_events_from_meetup.rb in the get_ends_at method, I can't see how the dates would come out wrong unless something incorrect was sent from meetup.

Their API states that the time and duration fields are in milliseconds, and the ruby Time module works in seconds. We're dividing by 1000 like we should be.

Anyways, maybe there will be more of a clue if I can see which events had the issue. Let me know!

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

No branches or pull requests

2 participants