[ruby-core:45552] [ruby-trunk - Bug #6571][Assigned] Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32

[ruby-core:45552] [ruby-trunk - Bug #6571][Assigned] Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32

[MartinBosslet (Martin Bosslet)]

Issue #6571 has been reported by MartinBosslet (Martin Bosslet).

----------------------------------------
Bug #6571: Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32
https://bugs.ruby-lang.org/issues/6571

Author: MartinBosslet (Martin Bosslet)
Status: Assigned
Priority: Normal
Assignee: luislavena (Luis Lavena)
Category: core
Target version: 2.0.0
ruby -v: ruby 1.9.3p125 (2012-02-16) [i386-mingw32]


This came up in https://bugs.ruby-lang.org/issues/6122.

Time.mktime(2038, 1, 19, 11, 14, 8) failed. To my understanding, 32 bit Time 
issues shouldn't occur in 1.9.3? I'm assigning this to Luis, maybe he knows
about this and what to do? Please feel free to reassign back to me. 


-- 
http://bugs.ruby-lang.org/

[ruby-core:45556] Re: [ruby-trunk - Bug #6571][Assigned] Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32

[Tanaka Akira]

2012/6/11 MartinBosslet (Martin Bosslet) <Martin.Bosslet@googlemail.com>:

> Time.mktime(2038, 1, 19, 11, 14, 8) failed. To my understanding, 32 bit Time
> issues shouldn't occur in 1.9.3? I'm assigning this to Luis, maybe he knows
> about this and what to do? Please feel free to reassign back to me.

I couldn't reproduce the problem on GNU/Linux (x86_64 and i686).

  % ./ruby -ve 'Time.mktime(2038, 1, 19, 11, 14, 8)'
  ruby 2.0.0dev (2012-06-11 trunk 36028) [x86_64-linux]

  % ./ruby -ve 'Time.mktime(2038, 1, 19, 11, 14, 8)'
  ruby 2.0.0dev (2012-06-11 trunk 36030) [i686-linux]

So it seems platform dependent issue.

However I think you should show the actual result (failure message) and
your timezone, though.

Note that my timzone is +0900 (JST).
-- 
Tanaka Akira

[ruby-core:45557] [ruby-trunk - Bug #6571][Feedback] Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32

[nobu (Nobuyoshi Nakada)]

Issue #6571 has been updated by nobu (Nobuyoshi Nakada).

Description updated
Status changed from Assigned to Feedback
Target version changed from 2.0.0 to 1.9.3

I can't reproduce it with 1.9.3p216, in JST and PST.
What are the failure message and your timezone?

----------------------------------------
Bug #6571: Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32
https://bugs.ruby-lang.org/issues/6571#change-27153

Author: MartinBosslet (Martin Bosslet)
Status: Feedback
Priority: Normal
Assignee: luislavena (Luis Lavena)
Category: core
Target version: 1.9.3
ruby -v: ruby 1.9.3p125 (2012-02-16) [i386-mingw32]


=begin
This came up in https://bugs.ruby-lang.org/issues/6122.

(({Time.mktime(2038, 1, 19, 11, 14, 8)})) failed. To my understanding, 32 bit Time 
issues shouldn't occur in 1.9.3? I'm assigning this to Luis, maybe he knows
about this and what to do? Please feel free to reassign back to me.
=end


-- 
http://bugs.ruby-lang.org/

[ruby-core:45558] Unsubscribe

[prathamesh joshi]

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: Type: text/html, Size: 164 bytes --]

[ruby-core:45559] [ruby-trunk - Bug #6571] Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32

[phasis68 (Heesob Park)]

Issue #6571 has been updated by phasis68 (Heesob Park).


I guess it is not an issue of Time#mktime but an issue of OpenSSL.
Furthermore, the description is inaccurate.

Here is my test with ruby 1.9.3p194 (2012-04-20) [i386-mingw32]
C:\Ruby193\bin>irb
irb(main):001:0> require 'OpenSSL'
=> true
irb(main):002:0> cert = OpenSSL::X509::Certificate.new
=> #<OpenSSL::X509::Certificate subject=, issuer=, serial=0, not_before=nil, not_after=nil>
irb(main):003:0> cert.not_after = Time.mktime(2038, 1, 19, 12, 14, 7)
=> 2038-01-19 12:14:07 +0900
irb(main):004:0> cert.not_after = Time.mktime(2038, 1, 19, 12, 14, 8)
RangeError: bignum too big to convert into `long'
        from (irb):4:in `not_after='
        from (irb):4
        from C:/Ruby193/bin/irb:12:in `<main>'
	
I think that this error due to time_to_time_t function defined in ext/openssl/ossl_asn1.c

time_t
time_to_time_t(VALUE time)
{
    return (time_t)NUM2LONG(rb_Integer(time));
}

----------------------------------------
Bug #6571: Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32
https://bugs.ruby-lang.org/issues/6571#change-27156

Author: MartinBosslet (Martin Bosslet)
Status: Feedback
Priority: Normal
Assignee: luislavena (Luis Lavena)
Category: core
Target version: 1.9.3
ruby -v: ruby 1.9.3p125 (2012-02-16) [i386-mingw32]


=begin
This came up in https://bugs.ruby-lang.org/issues/6122.

(({Time.mktime(2038, 1, 19, 11, 14, 8)})) failed. To my understanding, 32 bit Time 
issues shouldn't occur in 1.9.3? I'm assigning this to Luis, maybe he knows
about this and what to do? Please feel free to reassign back to me.
=end


-- 
http://bugs.ruby-lang.org/

[ruby-core:45560] [ruby-trunk - Bug #6571][Assigned] Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32

[nobu (Nobuyoshi Nakada)]

Issue #6571 has been updated by nobu (Nobuyoshi Nakada).

Status changed from Feedback to Assigned
Assignee changed from luislavena (Luis Lavena) to MartinBosslet (Martin Bosslet)
Target version changed from 1.9.3 to 2.0.0


----------------------------------------
Bug #6571: Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32
https://bugs.ruby-lang.org/issues/6571#change-27157

Author: MartinBosslet (Martin Bosslet)
Status: Assigned
Priority: Normal
Assignee: MartinBosslet (Martin Bosslet)
Category: core
Target version: 2.0.0
ruby -v: ruby 1.9.3p125 (2012-02-16) [i386-mingw32]


=begin
This came up in https://bugs.ruby-lang.org/issues/6122.

(({Time.mktime(2038, 1, 19, 11, 14, 8)})) failed. To my understanding, 32 bit Time 
issues shouldn't occur in 1.9.3? I'm assigning this to Luis, maybe he knows
about this and what to do? Please feel free to reassign back to me.
=end


-- 
http://bugs.ruby-lang.org/

[ruby-core:45576] [ruby-trunk - Bug #6571] Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32

[MartinBosslet (Martin Bosslet)]

Issue #6571 has been updated by MartinBosslet (Martin Bosslet).

Category changed from core to ext

Thanks for your analysis, guys. Makes sense now, why I couldn't reproduce it on 64 bits. The original #6122 did not contain the actual error that was raised, so thanks Heesob for pointing me towards the solution!
----------------------------------------
Bug #6571: Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32
https://bugs.ruby-lang.org/issues/6571#change-27173

Author: MartinBosslet (Martin Bosslet)
Status: Assigned
Priority: Normal
Assignee: MartinBosslet (Martin Bosslet)
Category: ext
Target version: 2.0.0
ruby -v: ruby 1.9.3p125 (2012-02-16) [i386-mingw32]


=begin
This came up in https://bugs.ruby-lang.org/issues/6122.

(({Time.mktime(2038, 1, 19, 11, 14, 8)})) failed. To my understanding, 32 bit Time 
issues shouldn't occur in 1.9.3? I'm assigning this to Luis, maybe he knows
about this and what to do? Please feel free to reassign back to me.
=end


-- 
http://bugs.ruby-lang.org/

[ruby-core:50622] [ruby-trunk - Bug #6571] Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32

[mghomn (Justin Peal)]

Issue #6571 has been updated by mghomn (Justin Peal).


Great thanks to all of you.
----------------------------------------
Bug #6571: Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32
https://bugs.ruby-lang.org/issues/6571#change-34464

Author: MartinBosslet (Martin Bosslet)
Status: Assigned
Priority: Normal
Assignee: MartinBosslet (Martin Bosslet)
Category: ext
Target version: 2.0.0
ruby -v: ruby 1.9.3p125 (2012-02-16) [i386-mingw32]


=begin
This came up in https://bugs.ruby-lang.org/issues/6122.

(({Time.mktime(2038, 1, 19, 11, 14, 8)})) failed. To my understanding, 32 bit Time 
issues shouldn't occur in 1.9.3? I'm assigning this to Luis, maybe he knows
about this and what to do? Please feel free to reassign back to me.
=end


-- 
http://bugs.ruby-lang.org/

[ruby-core:52456] [ruby-trunk - Bug #6571] Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32

[mame (Yusuke Endoh)]

Issue #6571 has been updated by mame (Yusuke Endoh).

Target version changed from 2.0.0 to next minor


----------------------------------------
Bug #6571: Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32
https://bugs.ruby-lang.org/issues/6571#change-36523

Author: MartinBosslet (Martin Bosslet)
Status: Assigned
Priority: Normal
Assignee: MartinBosslet (Martin Bosslet)
Category: ext
Target version: next minor
ruby -v: ruby 1.9.3p125 (2012-02-16) [i386-mingw32]


=begin
This came up in https://bugs.ruby-lang.org/issues/6122.

(({Time.mktime(2038, 1, 19, 11, 14, 8)})) failed. To my understanding, 32 bit Time 
issues shouldn't occur in 1.9.3? I'm assigning this to Luis, maybe he knows
about this and what to do? Please feel free to reassign back to me.
=end


-- 
http://bugs.ruby-lang.org/

[ruby-core:70758] [Ruby trunk - Bug #6571] Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32

[zzak]

Issue #6571 has been updated by Zachary Scott.

Assignee changed from Martin Bosslet to openssl

----------------------------------------
Bug #6571: Time.mktime Y2K38 problem on 1.9.3p125 i386-mingw32
https://bugs.ruby-lang.org/issues/6571#change-54137

* Author: Martin Bosslet
* Status: Assigned
* Priority: Normal
* Assignee: openssl
* ruby -v: ruby 1.9.3p125 (2012-02-16) [i386-mingw32]
* Backport: 
----------------------------------------
=begin
This came up in https://bugs.ruby-lang.org/issues/6122.

(({Time.mktime(2038, 1, 19, 11, 14, 8)})) failed. To my understanding, 32 bit Time 
issues shouldn't occur in 1.9.3? I'm assigning this to Luis, maybe he knows
about this and what to do? Please feel free to reassign back to me.
=end



-- 
https://bugs.ruby-lang.org/