-
Notifications
You must be signed in to change notification settings - Fork 60
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
SystemStackError (stack level too deep) - Issue with Braintree in production #80
Comments
Are you by any chance deploying with something like mina or capistrano? I'd guess so from the I ran into the same issue yesterday and spent some time debugging it. The issue is that the decorators are being loaded twice, meaning the alias here ends up aliasing itself rather than the original method: https://github.com/spree-contrib/spree_braintree_vzero/blob/3-1-stable/app/helpers/spree/admin/navigation_helper_decorator.rb#L2 The first time is from the The second time is from rails' eager loading. This means that the file gets required with two different paths. In my case:
Because one is from the symlinked directory and one is from the real location it get's required twice. As a workaround for this I created a fork which normalizes the path before loading it: builtbybuffalo@dabc805. That's working well for us now but I'm not sure how "correct" the fix is. A more appropriate solution may be to figure out why the paths are differing in the first place. |
@charlie-hadden Yea using Mina. After getting a couple of other people to look at it we determined much the same thing. Just couldn't figure out why it gets required twice, or what the nice solution would be, if there even is one. Seems like it should really support deployments via Mina or Cap, but I suppose lots of people just use Heroku? |
Is there any update regarding this bug? I am getting same one and above patch is also not working. |
Fix for SystemStackError (stack level too deep) issue in production (#80)
Fix for SystemStackError (stack level too deep) issue in production (spree-contrib#80)
Hey all.
I've not been able to have any success getting the Braintree v.zero gem to work in production without producing the following stack error.
This is a fresh un-altered version of spree 3.1.0 and the corrosponding 3-1-stable Braintree v.zero gem, running with rails 4.2.6.
It's only an issue in production (runs fine in development), and I just can't understand what's going on, I wonder if there's something wrong with this particular version, or if there's something else I'm missing.
The app is running via nginx + passenger, with ruby 2.3.1p112.
Any ideas?
The text was updated successfully, but these errors were encountered: