Skip to content

Ignore bad timestamps #83

Merged
merged 1 commit into from Sep 11, 2012

3 participants

@rsutphin

If something looks like a timestamp but has an invalid component, treat it as a string instead of throwing an ArgumentError.

This addresses issue #82.

@rsutphin rsutphin Ignore bad timestamps. #82.
If something looks like a timestamp but has an invalid component,
treat it as a string instead of throwing an ArgumentError.
0c478a1
@tenderlove tenderlove merged commit 08da2c2 into tenderlove:master Sep 11, 2012

1 check was pending

Details default The Travis build is in progress
@tiegz
tiegz commented on 0c478a1 Sep 27, 2012

thx for fixing this! Just ran into this case.

speaking of, do we know when the next version of this will be published? I tried to point to the github gem in bundler, but there was no gemspec :\

I can't speak to the next version of the gem, but I can offer the monkey patch I'm using for my affected Rails app for reference.

Another option might be to fork the repo, use rake to generate the gemspec, and commit it. Then you could point bundler at your fork. (I haven't tried this but it seems like it could work.)

perfect, thx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.