awkward silence

I don’t know if it’s rolled out to all servers yet, but the 2 I use are both at rails 0.13.1 now. I’ve got apps running on both that are doing great. This one has an unaltered typo, as well as an updated (new dispatcher, etc.) version of clubrs.

The fastcgi seems to be settling down very nicely. You can see below that the processes seem to be managed more sanely. To be fair, the processes exiting in the top entries are probably me killing them off to roll in the new changes to the production environment.

[Sat Jul 16 17:04:44 PDT 2005] Dispatcher failed to catch: exit (SystemExit)
  /usr/lib/ruby/1.8/fcgi.rb:10:in 'exit'
  /usr/lib/ruby/1.8/fcgi.rb:10
  /usr/lib/ruby/1.8/fcgi.rb:10:in 'call'
  /usr/lib/ruby/1.8/fcgi.rb:598:in 'each_cgi'
  /usr/lib/ruby/1.8/fcgi.rb:597:in 'each'
  /usr/lib/ruby/1.8/fcgi.rb:597:in 'each_cgi'
  dispatch.fcgi:18
FCGI process 14381 killed by this error

[Sat Jul 16 17:23:11 PDT 2005] Dispatcher failed to catch: SIGUSR1 (SignalException)
  /usr/lib/ruby/1.8/fcgi.rb:597:in 'each'
  /usr/lib/ruby/1.8/fcgi.rb:597:in 'each_cgi'
  dispatch.fcgi:18
FCGI process 10349 killed by this error

[16/Jul/2005:19:39:31 :: 29193] starting
[16/Jul/2005:19:39:32 :: 8639] starting
[16/Jul/2005:19:40:48 :: 21515] starting
[16/Jul/2005:19:45:10 :: 21515] terminated by explicit exit
[16/Jul/2005:19:47:29 :: 11480] starting
[16/Jul/2005:19:47:31 :: 29954] starting
[16/Jul/2005:19:53:29 :: 29954] terminated by explicit exit
[16/Jul/2005:20:10:43 :: 2931] starting
[16/Jul/2005:23:49:17 :: 2931] terminated by explicit exit
[16/Jul/2005:23:49:17 :: 2931] told to terminate NOW
[17/Jul/2005:05:29:47 :: 28109] starting
[17/Jul/2005:05:29:47 :: 12870] starting
[17/Jul/2005:05:37:09 :: 12870] terminated by explicit exit

A Test By Any Other Name

I really like this post on testing in rails. If you follow the pattern you end up with a nice set of tests and a bit of documentation to boot.

It looks to me like this will also help keep your objects focused. The naming convention would seem to help remind you of what the particular object ’should’ do.

And getting the free bit of documentation with the rake task is very cool!