"@marshal_with_utc_coercion": false?


#1

this is a debug on the @schedules variable which contains a bunch of
start and end times pulled from a mysql database.

attributes:
schedule_type: “7”
schedule_start: 2009-04-24 04:00:00
id: “21”
uid: “12”
schedule_end: 2009-04-24 11:00:00
attributes_cache:
schedule_start: !timestamp
at: “2009-04-24 04:00:00 -04:00”
@marshal_with_utc_coercion”: false
schedule_end: !timestamp
at: “2009-04-24 11:00:00 -04:00”
@marshal_with_utc_coercion”: false

i have no clue what this means… I’ve never gotten this one before.


#2

Morgan M. wrote:

this is a debug on the @schedules variable which contains a bunch of
start and end times pulled from a mysql database.

attributes:
schedule_type: “7”
schedule_start: 2009-04-24 04:00:00
id: “21”
uid: “12”
schedule_end: 2009-04-24 11:00:00
attributes_cache:
schedule_start: !timestamp
at: “2009-04-24 04:00:00 -04:00”
@marshal_with_utc_coercion”: false
schedule_end: !timestamp
at: “2009-04-24 11:00:00 -04:00”
@marshal_with_utc_coercion”: false

i have no clue what this means… I’ve never gotten this one before.

i thought i’d post the whole debug

  • !ruby/object:schedule
    attributes:
    schedule_type: “7”
    schedule_start: 2009-04-24 04:00:00
    id: “21”
    uid: “12”
    schedule_end: 2009-04-24 11:00:00
    attributes_cache:
    schedule_start: !timestamp
    at: “2009-04-24 04:00:00 -04:00”
    @marshal_with_utc_coercion”: false
    schedule_end: !timestamp
    at: “2009-04-24 11:00:00 -04:00”
    @marshal_with_utc_coercion”: false

#3

Jeremy K. wrote:

It’s Active Support fixing a bug in Ruby 1.8.x where UTC times are
incorrectly unmarshaled as local, not UTC, times.

So we flag that the time is UTC when it’s dumped and coerce it back to
UTC when it’s loaded.

jeremy

On Fri, Apr 24, 2009 at 12:03 PM, Morgan M.

i just noticed that it produces a page of errors in the error log.

Exception occurred during reader method compilation.
Maybe 11 is not a valid Ruby identifier?
compile error
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected tINTEGER
def 11; missing_attribute(‘11’, caller) unless
@attributes.has_key?(‘11’); @attributes[‘11’]; end
^
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected kEND, expecting $end
def 11; missing_attribute(‘11’, caller) unless
@attributes.has_key?(‘11’); @attributes[‘11’]; end
^
Exception occurred during reader method compilation.
Maybe 11 is not a valid Ruby identifier?
compile error
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected tINTEGER
def 11=(new_value);write_attribute(‘11’, new_value);end
^
Exception occurred during reader method compilation.
Maybe 11 is not a valid Ruby identifier?
compile error
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected tINTEGER
def 11?; query_attribute(‘11’); end
^
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected kEND, expecting $end
def 11?; query_attribute(‘11’); end
^
Exception occurred during reader method compilation.
Maybe 12 is not a valid Ruby identifier?
compile error
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected tINTEGER
def 12; missing_attribute(‘12’, caller) unless
@attributes.has_key?(‘12’); @attributes[‘12’]; end
^
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected kEND, expecting $end
def 12; missing_attribute(‘12’, caller) unless
@attributes.has_key?(‘12’); @attributes[‘12’]; end
^
Exception occurred during reader method compilation.
Maybe 12 is not a valid Ruby identifier?
compile error
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected tINTEGER
def 12=(new_value);write_attribute(‘12’, new_value);end
^
Exception occurred during reader method compilation.
Maybe 12 is not a valid Ruby identifier?
compile error
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected tINTEGER
def 12?; query_attribute(‘12’); end
^
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected kEND, expecting $end
def 12?; query_attribute(‘12’); end
^
Exception occurred during reader method compilation.
Maybe 13 is not a valid Ruby identifier?
compile error
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected tINTEGER
def 13; missing_attribute(‘13’, caller) unless
@attributes.has_key?(‘13’); @attributes[‘13’]; end
^
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected kEND, expecting $end
def 13; missing_attribute(‘13’, caller) unless
@attributes.has_key?(‘13’); @attributes[‘13’]; end
^
Exception occurred during reader method compilation.
Maybe 13 is not a valid Ruby identifier?
compile error
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected tINTEGER
def 13=(new_value);write_attribute(‘13’, new_value);end
^
Exception occurred during reader method compilation.
Maybe 13 is not a valid Ruby identifier?
compile error
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected tINTEGER
def 13?; query_attribute(‘13’); end
^
/Library/Ruby/Gems/1.8/gems/activerecord-2.2.2/lib/active_record/attribute_methods.rb:211:
syntax error, unexpected kEND, expecting $end
def 13?; query_attribute(‘13’); end
^

i don’t know if this is normal…


#4

So is there any way to make this stop happening that doesn’t involve
going back to an old version of rails.


#5

It’s Active Support fixing a bug in Ruby 1.8.x where UTC times are
incorrectly unmarshaled as local, not UTC, times.

So we flag that the time is UTC when it’s dumped and coerce it back to
UTC when it’s loaded.

jeremy

On Fri, Apr 24, 2009 at 12:03 PM, Morgan M.