Eventually exits with SystemStackError

[stouset]

It looks like your fix to #5 introduced another bug. After a day or two of leaving guard running, it exited with the following exception:

/Users/stouset/.rvm/gems/ruby-1.9.2-p0@patterns2/bin/guard:19: stack level too deep (SystemStackError)

[thibaudgg]

That's weird. Can you give more backtrace? bin/guard:19 only isn't very helpfull. Thx!

[stouset]

It didn't give me one. Unfortunately, it will probably take another few days before I can reproduce this.

[thibaudgg]

Ok, I'll also try to reproduce this on my side.

[yannlugrin]

I test this case on linux too

[thibaudgg]

Still having this issue? I haven't been able to reproduce it.

[stouset]

I haven't noticed it in a bit, but I've been away at RubyConf. I'll let you know if I see it in the next day or two.

[mordaroso]

This exception pops up when I change a lot of files in a short period.
For example when I populate sample data that is indexed with thinking sphinx.

I can reproduce the problem with following shell command:
for i in {0..100000}; do touch tmp/dummy$i.txt;rm tmp/dummy$i.txt; done

[thibaudgg]

Ok, we could avoid that by adding an option to exclude some files extensions. Sounds good for you?

[thibaudgg]

still needed with 0.4.0?

[stouset]

Nope. Haven't seen the problem return in a long, long while.

[surajreddy]

I'm getting this error on a windows install - everything's working fine on our mac machines, but we get this on Windows:
c:/Ruby192/lib/ruby/gems/1.9.1/bin/guard:19: stack level too deep (SystemStackError)

[surajreddy]

On a different app, I get these errors recursively (can't see the top):

from c:/Ruby192/lib/ruby/gems/1.9.1/gems/guard-0.4.0/lib/guard/ui.rb:8:in `info'
        from c:/Ruby192/lib/ruby/gems/1.9.1/gems/guard-0.4.0/lib/guard/ui.rb:59:in `rescue in color_enabled?'
        from c:/Ruby192/lib/ruby/gems/1.9.1/gems/guard-0.4.0/lib/guard/ui.rb:55:in `color_enabled?'
        from c:/Ruby192/lib/ruby/gems/1.9.1/gems/guard-0.4.0/lib/guard/ui.rb:45:in `color'
        from c:/Ruby192/lib/ruby/gems/1.9.1/gems/guard-0.4.0/lib/guard/ui.rb:41:in `reset_color'

[surajreddy]

Commenting line #8 in ui.rb seems to fix this for me on windows:
#puts reset_color(message) if message != ''

Also, I had to replace interactor with https://raw.github.com/guard/guard/master/lib/guard/interactor.rb

[thibaudgg]

Great, please can you provide a pull request to fix this. Thx!

[surajreddy]

done - however, please note that I don't know what I'm doing/I see this as a temp fix only.

[jeffdeville]

I just had the same problem, but I was able to fix it by installing the win32console gem. I think that the problem is that if this gem is missing it, it tries to tell you that it's missing it... by using it. (color_reset). I think the easiest fix may simply to update the docs on how to get guard up and running with windows. You may want to suggest including:
gem 'rb-fchange'
gem 'win32console'
gem 'rb-notifu'
into windows-based Gemfiles.

[surajreddy]

Thanks #jeff! We'll try that out.

[ajlitzin]

gem install win32console also worked for getting me past the "stack level too deep" error when running guard