-
Notifications
You must be signed in to change notification settings - Fork 551
Fix incorrect use of Process::exit. This fixes open issue #244. #578
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
Conversation
Unlike the C library function exit(), Ruby's version takes a boolean, not an integer. Added a spec to check the actual shell-level exit value of a Thor script, and fixed calls to Process::exit.
The build for 1.8.7 fails with problems in the webmock gem. As far as I can see, my change didn't cause these; does the current head build for 1.8.7 in CI correctly? |
#583 fixes the travis error that shows up here. |
@rafaelfranca What do you think about this? Backwards compatibility considerations about changing the default for this setting apart, this is fixing an actual bug, right? |
Would it help if I rebase this PR and get it green? According to #244 (comment), even setting |
@rafaelfranca Since you're having a look at |
Thanks! ❤️ The tests need to be skipped on 1.8.7 due to using |
Yes. Skipping is fine |
Ok, I'll open a separate PR to get it green! |
Funny, while creating the PR to skip the tests on 1.8.7 I tried reverting the code changes in this PR and the specs still passed. So it seems that this PR didn't fix anything and the |
🌈
Unlike the C library function exit(), Ruby's version takes a boolean,
not an integer. Added a spec to check the actual shell-level exit
value of a Thor script, and fixed calls to Process::exit.