Aaron Kromer

> I actually like to add `--require rails_helper` to a `.rspec` file in my project root. It's fine to choose to do this. Just be aware that there is a...

> I'll typically extract these out into separate gems with their own specs, leaving very few specs (if any) where I don't need Rails. Yep, @chrisvfritz that's a completely valid...

Yes, great convo! :smile: I should note that I do use `bin/rspec --require rails_helper` when I run on CI. I also have a local alias `bspecr` for that, when I...

FWIW I also tested with Ruby 1.9.3-p392 and it did not have this problem.

It looks like the current `master` branch fixes this issue. It was related to #70. When is the next patch release planned?

@BM5k do you know the differences in the rational seconds? As a work around, you can use the RSpec [`be_within`](https://www.relishapp.com/rspec/rspec-expectations/v/2-14/docs/built-in-matchers/be-within-matcher) matcher: `user.reload.deleted_at.should be_within(1.second).of(Time.zone.now)` Taking a peak at master, it seems...

@BM5k one other thing to be aware of, is that some databases will strip the fractional seconds. This could just be a DB issue. So when the value is read...

@BM5k would be interesting to add some `puts` for `Time.zone.now.nsec` and `user.reload.deleted_at.nsec` before the `should` line to see what CI says.

In the binding, if you run the expression on line 193 what happens? You may need to start taking apart the different fields. :grimacing: Also, could you paste how the...

> if we did this, maybe we should just make it emit a loud warning at the end but still run the spec file. That would not be a breaking...