-
Notifications
You must be signed in to change notification settings - Fork 10
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
Does not support 1.9.2 #1
Comments
thats the last problem. just put the actual lib into separate file and require it (don't forget to install highline), but it won't work either. internals in ruby 1.9.2 changed and raise can't be overriden easily. |
Actually it has nothing to do really with Ruby 1.9.2 raise internals. If interested have a look at #2 Hopefully Avdi will like it :-) |
i've took a look and i didn't see the fix for the issue. what i've meant is that C modules will still raise usual exceptions. |
Daniel, our fix deals as it describes with the problem of Hammertime 0.0.2 not handling Ruby exceptions such as LoadError inside the hammertime_raise which was the cause for breakage when attempting to run it on 1.9.x. The issue with Hammertime not dealing with C exceptions in general remains, but this was never a problem in porting Hammertime to Ruby 1.9.2. Our fix makes Hammertime run on 1.9.x and covers some other corner cases as well. |
Cannot install with Ruby 2.2.2.... Using pry until can... no big deal.
Can't handle 1.9.x yet Provided configuration options: extconf failed, exit code 1 |
Getting this as well, did you find a solution @paradisaeidae ? |
Hi Cheerful, |
Thanks ;) I was hoping to use hammertime because it automatically captures exceptions in any process and lets you go into an irb session. I was running a rake task and I didn't want to have to go to the bother of drilling down to where the error was happening and putting in a pry |
We tried to bundle with the hammertime gem under 1.9.2-p180 and got the following:
Sadly, it looks like there is a dependency on 1.8.7 :(
Kevin & Daniela
Pivotal Labs, Inc.
The text was updated successfully, but these errors were encountered: