You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is a hello world apotomo application that demonstrates a bug that popped up when upgrading from journey 1.0.3 to 1.0.4 (rails 3.2.7 is going to require 1.0.4 so we need to fix this):
I made an issue over on the journey issue tracker as I originally thought it was a journey bug but I am unable to reproduce it without bringing apotomo and rspec-apotomo into the mix:
Here is a hello world apotomo application that demonstrates a bug that popped up when upgrading from journey 1.0.3 to 1.0.4 (rails 3.2.7 is going to require 1.0.4 so we need to fix this):
https://github.com/atambo/journeyapotomobug
I made an issue over on the journey issue tracker as I originally thought it was a journey bug but I am unable to reproduce it without bringing apotomo and rspec-apotomo into the mix:
rails/journey#42
The text was updated successfully, but these errors were encountered: