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

Error when rspec loads files using Refinements #3820

Closed
estolfo opened this Issue Apr 21, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@estolfo

estolfo commented Apr 21, 2016

Summary

Mongoid has supported JRuby until now but I've run into some issues when refactoring Mongoid to use Refinements instead of monkey-patching core classes.

The Refinements branch in Mongoid is here.

I believe I'm seeing the same issue as this one.

It seems that a problem is encountered when files are loaded by rspec. The line throwing the error is here.

If I put the line "using Refinements" after the culprit line, it will load with no errors.

Let me know if I can help with debugging. If you would like to test, you can clone the Mongoid repo, check out the 6.0.0-refinements branch, start mongod on the default host/port (localhost:27017), run bundle, and then rspec.

Environment

@headius

This comment has been minimized.

Show comment
Hide comment
@headius

headius Apr 22, 2016

Member

I believe this will be fixed, but I'm not sure if things run properly. You'll see a commit for 9.1 shortly, and if you have a chance to test a 9.1 snapshot before we release next week it would be a great help.

If there's still outstanding issues that aren't the arity/block error, file a new issue and we'll look at it for 9.1.1.

Member

headius commented Apr 22, 2016

I believe this will be fixed, but I'm not sure if things run properly. You'll see a commit for 9.1 shortly, and if you have a chance to test a 9.1 snapshot before we release next week it would be a great help.

If there's still outstanding issues that aren't the arity/block error, file a new issue and we'll look at it for 9.1.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment