Skip to content
This repository

Stack level too deep #75

Open
eturk opened this Issue October 19, 2011 · 10 comments

7 participants

Ethan Turkeltaub germs12 Anton Lindqvist ExtractMethod LTD oren Yura Omelchuk Nate Miller
Ethan Turkeltaub

When I run CIJoe with Sinatra 1.2.7, I'm getting this:

:public is no longer used to avoid overloading Module#public, use :public_folder instead
    from /home/ethan/.rvm/gems/ruby-1.9.2-p290@fhsclock/gems/cijoe-0.9.2/lib/cijoe/server.rb:12:in `<class:Server>'
/home/ethan/.rvm/gems/ruby-1.9.2-p290@fhsclock/bin/cijoe:19: stack level too deep (SystemStackError)

The first error is easily fixable, but I'm not sure what the deal is with the SystemStackError.

germs12

I got the same thing this morning on my first run. I'm happy to help debug, but this is my first time using CIJoe.

:public is no longer used to avoid overloading Module#public, use :public_folder instead
from /Users/jamesthullbery/.rvm/gems/ruby-1.9.2-p180@cijoe/gems/cijoe-0.9.2/lib/cijoe/server.rb:12:in `class:Server'
/Users/jamesthullbery/.rvm/gems/ruby-1.9.2-p180@cijoe/bin/cijoe:19: stack level too deep (SystemStackError)

Anton Lindqvist

Probably due to this bug.

Ethan Turkeltaub

Looks like it. ETA on merge into master?

Anton Lindqvist

Sorry. Can't tell since I'm not the owner.

ExtractMethod LTD

I got the same problem. Installing sinatra 1.2.0 seems to have resolved this for me. Maybe the gemspec can be updated to specify the sinatra version.

Anton Lindqvist

Ok, thanks for the info.

oren

sinatra 1.2 didn't work for me. 1.2.7 seems to be fine.

Yura Omelchuk

Got same problem with sinatra 1.3.1

~/rails/jw_walls$ cijoe .

:public is no longer used to avoid overloading Module#public, use :public_folder instead
from /home/jurgen/.rvm/gems/ruby-1.9.3-p0@rails3/gems/cijoe-0.9.2/lib/cijoe/server.rb:12:in `class:Server'
/home/jurgen/.rvm/gems/ruby-1.9.3-p0@rails3/bin/cijoe:19: stack level too deep (SystemStackError)

gem list sinatra
*** LOCAL GEMS ***
sinatra (1.3.1)

Nate Miller

Looks like this happens when Sinatra has problems binding with port 4567. I ran into the same issue on a machine that had a firewall blocking this port.

Yura Omelchuk

There should not be any binding problems with my setup. Works fine with Sinatra 1.2.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.