-
Notifications
You must be signed in to change notification settings - Fork 270
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
Task deploy:migrate exists with SystemStackError (version 1.6.0) #246
Comments
@the-undefined this seems to be related to your changes in #242. Can you help? |
@Flauschbaellchen thanks for the detailed report. I'll try to get this sorted ASAP. |
Seems add |
Alrighty I will get that fix in shortly. Thanks! |
I've released 1.6.1 with a fix. Can you verify it works? |
it works at v1.6.1 without add extra one line code now, nice! |
Sorry I missed this! I forgot to test without the override in, which I could have done on a different app now I think about it 🤦 Thank you both for reporting and turning around a fix super quickly! |
Steps to reproduce
Updating to capistrano-rails 1.6.0.
Expected behavior
Task deploy:migrate should run successfully.
Actual behavior
Task deploy:migrate runs into a recursive loop, exits with "stack level too deep":
System configuration
Capistrano gems:
The text was updated successfully, but these errors were encountered: