Ruby on Rails Tuesday, September 2, 2014

Thank you Jason for your fast reply. I didn't know about the default
logger, I have changed my code. Yes it is in a controller, in the create
action: https://gist.github.com/anonymous/d138a4f2c76bb4b32dd2

The full log:
Started POST "/game" for 127.0.0.1 at 2014-09-03 00:14:49 +0200
Processing by GameController#create as HTML
Parameters: {"utf8"=>"V",
"authenticity_token"=>"gx7TovN+tZbMxOTc91l5P/5jqviBx
eO9vlJQaxJ19No=", "game"=>{"small_blind"=>"1", "big_blind"=>"2",
"player_number"
=>"2"}, "commit"=>"New game !"}
cards
#<ActiveRecord::Associations::CollectionProxy::ActiveRecord_Associations_Collect
ionProxy_Card:0x3b762e8>
0
players
Completed 500 Internal Server Error in 114ms

SyntaxError
(C:/site/app/models/player.rb:48: voi
d value expression):
app/controllers/game_controller.rb:11:in `create'


Rendered
C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/actionpack-4.0.2
/lib/action_dispatch/middleware/templates/rescues/_source.erb (42.0ms)
Rendered
C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/actionpack-4.0.2
/lib/action_dispatch/middleware/templates/rescues/_trace.erb (7.0ms)
Rendered
C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/actionpack-4.0.2
/lib/action_dispatch/middleware/templates/rescues/_request_and_response.erb
(9.0
ms)
Rendered
C:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/actionpack-4.0.2
/lib/action_dispatch/middleware/templates/rescues/diagnostics.erb within
rescues
/layout (214.1ms)

--
Posted via http://www.ruby-forum.com/.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/76fb6cc467833a0c12eee3f00729416f%40ruby-forum.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment