Bug #4571 closed
YAML.load given an ISO8601 timestamp creates an incorrect value for usec
Added by brixen (Brian Shirai) about 14 years ago.
Updated about 14 years ago.
Description
=begin
$ ruby1.8.7 -v -ryaml -e 'p YAML.load("2011-03-22t23:32:11.000000342222+01:00").usec'
ruby 1.8.7 (2011-02-18 patchlevel 334) [i686-darwin9.8.0]
342222
$ ruby1.9.2 -v -ryaml -e 'p YAML.load("2011-03-22t23:32:11.000000342222+01:00").usec'
ruby 1.9.2p180 (2011-02-18 revision 30909) [i386-darwin9.8.0]
342222
$ ruby1.9 -v -ryaml -e 'p YAML.load("2011-03-22t23:32:11.000000342222+01:00").usec'
ruby 1.9.3dev (2011-04-12 trunk 31263) [i386-darwin9.8.0]
342222
I believe these should be 0.
Thanks,
Brian
=end
Files
noname (500 Bytes)
noname
tenderlovemaking (Aaron Patterson), 05/06/2011 08:23 AM
Category set to ext
Status changed from Open to Assigned
Assignee set to tenderlovemaking (Aaron Patterson)
Hi Aaron, how do you feel the patch?
I can pull it when you are OK.
ruby -v changed from ruby 1.9.3dev (2011-04-12 trunk 31263) [i386-darwin9.8.0] to -
Status changed from Assigned to Closed
% Done changed from 0 to 100
This issue was solved with changeset r31441.
Brian, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
YAML.load time correctly parse usecs smaller than 1 fixes #4571
Signed-off-by: URABE, Shyouhei [email protected]
Also available in: Atom
PDF
Like 0
Like 0 Like 0 Like 0 Like 0 Like 0