We were using version 1.4.1 which contained a bug that would prevent proper error reporting when an initializer or auto-loaded gem resulted in an LoadError being raised and uncaught.
@kariabancroft It looks like we just hit a bit of bad luck. You started this project on Nov 12th, 2015 and the fix for this bug (in version 1.4.2) was release on the 16th.
We were using version 1.4.1 which contained a bug that would prevent proper error reporting when an initializer or auto-loaded gem resulted in an LoadError being raised and uncaught.
@kariabancroft It looks like we just hit a bit of bad luck. You started this project on Nov 12th, 2015 and the fix for this bug (in version 1.4.2) was release on the 16th.