Eventually exits with SystemStackError about guard HOT 18 CLOSED

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

from guard.

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

from guard.

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

from guard.

I test this case on linux too

from guard.

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

from guard.

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.

from guard.

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

from guard.

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

from guard.

still needed with 0.4.0?

from guard.

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

from guard.

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)

from guard.

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'

from guard.

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

from guard.

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

from guard.

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

from guard.

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.

from guard.

Thanks #jeff! We'll try that out.

from guard.

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

from guard.