Hello list,
when running the following simple Ruby-Program:
require 'rubygems' require 'active_support'
using Command+R, I get the following output:
/Library/Ruby/Gems/1.8/gems/builder-2.1.2/lib/blankslate.rb:84:in `blank_slate_method_added': stack level too deep (SystemStackError) from /Library/Ruby/Gems/1.8/gems/builder-2.1.2/lib/blankslate.rb: 84:in `blank_slate_method_added' from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/ builder.rb:86:in `method_added' from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/ builder.rb:111 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `require' from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/ active_support/core_ext/array/conversions.rb:1 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `require' ... 8 levels... from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/ active_support.rb:30 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:32:in `gem_original_require' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:32:in `require' from /Users/cypher/Projects/test.rb:2 /Library/Ruby/Gems/1.8/gems/builder-2.1.2/lib/blankslate.rb:84:in `blank_slate_method_added': stack level too deep (SystemStackError) from /Library/Ruby/Gems/1.8/gems/builder-2.1.2/lib/blankslate.rb: 84:in `blank_slate_method_added' from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/ builder.rb:86:in `method_added' from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/ builder.rb:111 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `require' from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/ active_support/core_ext/array/conversions.rb:1 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:27:in `require' ... 8 levels... from /Library/Ruby/Gems/1.8/gems/activesupport-2.0.2/lib/ active_support.rb:30 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:32:in `gem_original_require' from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:32:in `require' from /Users/cypher/Projects/test.rb:2
(OS X.5, default Ruby 1.8.6p111, TextMate Build 1436)
The problem is that both the builder-gem and TextMate's builder.rb try to alias method_added to blank_slate_method_added. I've patched TM's builder.rb to alias to tm_blank_slate_method_added instead, which works. However, this is only a hack to fix this problem, I'm sure there is a better way to address this (e.g. builder.rb checking wether a module 'Builder' already exists, and if not, load tm_builder.rb or something like that).
regards, Markus
On 23 Dec 2007, at 19:45, Markus Prinz wrote:
[...] The problem is that both the builder-gem and TextMate's builder.rb try to alias method_added to blank_slate_method_added. I've patched TM's builder.rb to alias to tm_blank_slate_method_added instead, which works. However, this is only a hack to fix this problem, I'm sure there is a better way to address this (e.g. builder.rb checking wether a module 'Builder' already exists, and if not, load tm_builder.rb or something like that).
Could you try revert your local changes and svn checkout latest Ruby bundle, see if that still gives you a problem?
On 23.12.2007, at 19:50, Allan Odgaard wrote:
On 23 Dec 2007, at 19:45, Markus Prinz wrote:
[...]
Could you try revert your local changes and svn checkout latest Ruby bundle, see if that still gives you a problem?
Would GetBundle's "Update Installed Bundles" update the Ruby bundle to the latest version as well?
regards, Markus
On 23 Dec 2007, at 19:57, Markus Prinz wrote:
[...]
Could you try revert your local changes and svn checkout latest Ruby bundle, see if that still gives you a problem?
Would GetBundle's "Update Installed Bundles" update the Ruby bundle to the latest version as well?
No, see http://blog.macromates.com/2006/updating-a-bundle/ for the best way to update a default bundle.
On 23.12.2007, at 20:05, Allan Odgaard wrote:
On 23 Dec 2007, at 19:57, Markus Prinz wrote:
[...]
Could you try revert your local changes and svn checkout latest Ruby bundle, see if that still gives you a problem?
Would GetBundle's "Update Installed Bundles" update the Ruby bundle to the latest version as well?
No, see http://blog.macromates.com/2006/updating-a-bundle/ for the best way to update a default bundle.
Thanks.
After reverting my changes and updating the Ruby bundle, I no longer see the error.
regards, Markus
I'm having the same error message. However it's triggered when I run a foccussed unit test in my Rails 2.0.2 project. (Other projects with different Rails versions are ok, also Cmd-R to run all tests is fine).
I've reloaded my Ruby Bundle. I've checked my Ruby paths are being set correctly (creating .MacOSX/environment.plist also) I've renamed Textmate's builder to Builder.rb.off as suggested in a blog
I still get the error...
Any ideas?
Thanks in advance.
Josh
Markus Prinz wrote:
On 23.12.2007, at 20:05, Allan Odgaard wrote:
On 23 Dec 2007, at 19:57, Markus Prinz wrote:
[...]
Could you try revert your local changes and svn checkout latest Ruby bundle, see if that still gives you a problem?
Would GetBundle's "Update Installed Bundles" update the Ruby bundle to the latest version as well?
No, see http://blog.macromates.com/2006/updating-a-bundle/ for the best way to update a default bundle.
Thanks.
After reverting my changes and updating the Ruby bundle, I no longer see the error.
regards, Markus
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
-
Allan Odgaard -
Josh Price -
Markus Prinz