ok, that's a big headline for something I can't repeat but its the only way I know how to classify this stacktrace (context info follows):
merb : worker (port 4000) ~ invalid date - (ArgumentError) /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/ 1.8/date.rb:1482:in `new' ./lib/core_extensions.rb:28:in `to_datetime' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/ 1.8/date.rb:1627:in `__send__' /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/ 1.8/date.rb:1627:in `now' /Library/Ruby/Gems/1.8/gems/dm-timestamps-0.9.7/lib/dm-timestamps.rb:9 /Library/Ruby/Gems/1.8/gems/dm-timestamps-0.9.7/lib/dm-timestamps.rb: 25:in `[]' /Library/Ruby/Gems/1.8/gems/dm-timestamps-0.9.7/lib/dm-timestamps.rb: 25:in `set_timestamp_properties' /Library/Ruby/Gems/1.8/gems/dm-timestamps-0.9.7/lib/dm-timestamps.rb: 24:in `each' /Library/Ruby/Gems/1.8/gems/dm-timestamps-0.9.7/lib/dm-timestamps.rb: 24:in `set_timestamp_properties' /Library/Ruby/Gems/1.8/gems/extlib-0.9.8/lib/extlib/hook.rb:256:in `execute_before_save_nan_hook_stack' /Library/Ruby/Gems/1.8/gems/extlib-0.9.8/lib/extlib/hook.rb:293:in `save' /Library/Ruby/Gems/1.8/gems/extlib-0.9.8/lib/extlib/hook.rb:292:in `catch' /Library/Ruby/Gems/1.8/gems/extlib-0.9.8/lib/extlib/hook.rb:292:in `save' /Users/jhancock/src/ssmerb.git/app/models/user.rb:242:in `register_new_user' /Users/jhancock/src/ssmerb.git/app/controllers/users.rb:43:in `create' /Library/Ruby/Gems/1.8/gems/merb-action-args-1.0.1/lib/merb-action- args/abstract_controller.rb:40:in `__send__' /Library/Ruby/Gems/1.8/gems/merb-action-args-1.0.1/lib/merb-action- args/abstract_controller.rb:40:in `_call_action' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core/controller/ abstract_controller.rb:285:in `_dispatch' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core/controller/ merb_controller.rb:191:in `_dispatch' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core/dispatch/ dispatcher.rb:102:in `dispatch_action' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core/dispatch/ dispatcher.rb:74:in `handle' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core/dispatch/ dispatcher.rb:36:in `handle' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core/rack/ application.rb:17:in `call' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core/rack/ middleware/static.rb:28:in `call' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core/rack/handler/ mongrel.rb:82:in `process' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:159:in `process_client' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `each' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `process_client' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `initialize' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `new' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `initialize' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `new' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `run' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core/rack/adapter/ mongrel.rb:38:in `start_server' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core/rack/adapter/ abstract.rb:235:in `start_at_port' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core/rack/adapter/ abstract.rb:85:in `start' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core/server.rb: 174:in `bootup' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core/server.rb: 42:in `start' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/lib/merb-core.rb:169:in `start' /Library/Ruby/Gems/1.8/gems/merb-core-1.0.1/bin/merb:11 /usr/bin/merb:19:in `load' This happened during testing the registration of a new user. The code in the model has been unchanged for a long time. In this usage, I create a new User, set a couple of attributes, including a timestamp using Time.now() and then save the user. This stacktrace seems to indicate that somehow a time object was created that later didn't work well for `to_datetime'. I was able to re-run the code and not have the error again. This has never been seen before and its a bit unnerving. Any ideas? Jon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
