resque-web status page exceptions with Ruby 1.9.1

[kuroneko]

I get the following exception when trying to view the status page in resque-web. Works correctly under ruby 1.8.7 on same machine with same gem versions.

NameError - uninitialized constant Resque::Server::VIEW_PATH:
/usr/local/rvm/gems/ruby-1.9.1-p378/gems/resque-status-0.1.4/lib/resque/status_server.rb:38:in status_view' /usr/local/rvm/gems/ruby-1.9.1-p378/gems/resque-status-0.1.4/lib/resque/status_server.rb:23:inblock in registered'
/usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:865:in call' /usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:865:inblock in route'
/usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:521:in instance_eval' /usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:521:inroute_eval'
/usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:500:in block (2 levels) in route!' /usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:497:incatch'
/usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:497:in block in route!' /usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:476:ineach'
/usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:476:in route!' /usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:601:indispatch!'
/usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:411:in block in call!' /usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:566:ininstance_eval'
/usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:566:in block in invoke' /usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:566:incatch'
/usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:566:in invoke' /usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:411:incall!'
/usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:399:in call' /usr/local/rvm/gems/ruby-1.9.1-p378/gems/rack-1.1.0/lib/rack/showexceptions.rb:24:incall'
/usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:979:in block in call' /usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:1005:insynchronize'
/usr/local/rvm/gems/ruby-1.9.1-p378/gems/sinatra-1.0/lib/sinatra/base.rb:979:in call' /usr/local/rvm/gems/ruby-1.9.1-p378/gems/rack-1.1.0/lib/rack/content_length.rb:13:incall'
/usr/local/rvm/gems/ruby-1.9.1-p378/gems/rack-1.1.0/lib/rack/handler/webrick.rb:48:in service' /usr/local/rvm/rubies/ruby-1.9.1-p378/lib/ruby/1.9.1/webrick/httpserver.rb:111:inservice'
/usr/local/rvm/rubies/ruby-1.9.1-p378/lib/ruby/1.9.1/webrick/httpserver.rb:70:in run' /usr/local/rvm/rubies/ruby-1.9.1-p378/lib/ruby/1.9.1/webrick/server.rb:183:inblock in start_thread'

Gem versions are as follows:
redis (2.0.5)
resque (1.9.9)
resque-status (0.1.4)
sinatra (1.0)
rack (1.1.0)

[quirkey]

This should be fixed with the latest release. Please test and let me know! Thanks