You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Time.new reads an offset of -0000 or -00 as +00:00 rather than UTC, unlike CRuby, and so does Time.iso8601 since 10.1.3.0 #10016
Time.new reads an offset of -0000 or -00 as a fixed offset of zero, +00:00, where CRuby reads it as UTC, as both read -00:00. This applies to the String form, such as Time.new("2026-10-31T09:30:00-0000"), and to the zone argument, such as Time.new(2026, 10, 31, 9, 30, 0, "-0000").
Up to JRuby 10.1.2.0 this did not show through Time.iso8601, since the time gem 0.4.2 read the offset itself. JRuby 10.1.3.0 bundles the time gem 0.5.0, whose Time.xmlschema (and so Time.iso8601) hands the text to Time.new on Ruby 3.2 and later (Time._xmlschema in time.rb), so Time.iso8601("2026-10-31T09:30:00-0000").utc? changed from true to false in 10.1.3.0. CRuby 4.0.7 with the time gem 0.5.0 still returns true, since its Time.new reads -0000 as UTC.
As CRuby: -0000 and -00 are UTC, like -00:00 and Z, while +0000 keeps an offset of zero. RFC 3339 (section 4.3) and RFC 2822 (section 3.3) use -00:00 and -0000 for a time in UTC whose local offset is not known. Code that tells UTC from +00:00, for example to write Z rather than +00:00, reads the same text differently on JRuby, and since 10.1.3.0 through Time.iso8601 too.
Environment
JRuby 10.0.7.0 (3.4.5), 10.1.2.0 (4.0.0) and 10.1.3.0 (4.0.9), OpenJDK 25.0.2, macOS arm64. CRuby 3.4.11 and 4.0.7 for comparison.
Activity
Code Review: advise jruby-openssl 0.19.4 for SFTP on JRuby, and link …