I've added a failing spec to trigger the custom_namespace error on the form builder as discussed in issue #998
Add a spec that triggers a threaded error with the form builder
Remove custom_namespace spec and commit on branch
Add spec for custom_namespace error
When building a large number of forms in a threaded environment,
I see the following error.
"undefined method `custom_namespace' for Formtastic::FormBuilder:Class"
Set travis to test in jruby 1.9
@hudson-gev-art are the failure errors you're seeing on Travis what you were expecting and what you saw locally? I'm guessing not. We might need to add JRuby to the build matrix as part of this work.
Simplify test matrix - Focus on jruby
The travis error is different than what I was seeing. Looks like this issue may be jruby specific.
I added jruby to the build matrix on my fork. You can check out the build https://travis-ci.org/hudson-gev-art/formtastic/jobs/19999829
The custom_namespace issue is there as well as a few other issues that manifested in the different environment. I'm not sure what you think the next steps should be ( if any ) but I'll offer as much help as I can. Thanks,
Hey there @hudson-gev-art. We need someone familiar with jruby to get in there and see if they can make progress on any of those failing tests. I can ask @charliesome if he has any ideas on the threading issue with the class attributes on Builder (custom_namespace, etc), but in order to support jruby, we really need someone to champion it and maybe even join the core group.
If you're up for the challenge, I'd be thrilled to see wider support.
Compared to other open PRs and issues, I don't think I'm going to be able to make progress on this for quite a while.
Thanks for looking into this. I've closed the issue for now as it will take me some time to familiarize myself with the code enough to start looking into the jruby issues.
Closing for now, we're not actively making progress on this, but more than happy to re-open when we do.