Bug #14860: Time.strptime does not work with Julian dates using %j

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: 2.5.1
• Backport: 2.3: REQUIRED, 2.4: REQUIRED, 2.5: REQUIRED

[ajrkerr (Adam Kerr)]

Time.strptime does not appear to be handling Julian dates, it is defaulting the date to be whatever is provided as "now" (e.g. January 1). I believe this is because Time is calling Date._strptime which returns a hash with {:yday=> ...} and does not handle the yday keyword.

Found in 2.3.3, verified not working in 2.5.1.

require "time"
require "date"

### Works for Dates ###
parsed_date = Date.strptime("15300", "%y%j")
expected_date = Date.new(2015, 10, 27)
# Does not raise
raise "dates not equal" if expected_date != parsed_date


### Does not work for Time ###
parsed_time = Time.strptime("15300", "%y%j")
expected_time = Time.new(2015, 10, 27)
# Raises
raise "times not equal" if expected_time != parsed_time

[nobu (Nobuyoshi Nakada)]

• Has duplicate Bug #14933: Time.strptime with ordinal dates added

[nobu (Nobuyoshi Nakada)]

• Status changed from Open to Closed

Applied in changeset trunk|r64028.

---

time.rb: yday support

• lib/time.rb (Time.make_time): added yday support.
  [ruby-core:87545] [Bug #14860]

[nagachika (Tomoyuki Chikanaga)]

• Backport changed from 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN to 2.3: REQUIRED, 2.4: REQUIRED, 2.5: REQUIRED

[nobu (Nobuyoshi Nakada)]

• Related to Bug #15776: Difference between Time.parse behaviour between 2.6.0 and 2.6.1+ added