setSeconds doesn't work correct with time conversion

[sruetzler]

• Version: 4.4.5
• Platform: Ubuntu 14.04.4 x63:64
• Subsystem:

The problem still exists in 6.2.0

Tested in Timezone Europe/Berlin
Example Code:

date = new Date(1445734861000); //Sun Oct 25 2015 02:01:01 GMT+0100 (CET)
//Right after switching daylight saving off

date.setSeconds(0) //Sun Oct 25 2015 02:01:00 GMT+0200 (CEST)
date.getTime() //1445731260000

The date is now almost one hour before switching daylight saving off.
Expected date: Sun Oct 25 2015 02:01:00 GMT+0100 (CET)
At least in v0.10.32 this works.

[targos]

Looks like it is related to the following V8 bug: https://bugs.chromium.org/p/v8/issues/detail?id=3637&q=setSeconds&colspec=ID%20Type%20Status%20Priority%20Owner%20Summary%20HW%20OS%20Component%20Stars

[sruetzler]

Yes I think this is the same problem.
The V8 issue priority is medium and it's open since Oct 2014.
For us this is a critical error is there a known workaround for this problem.

[jasnell]

@targos ... is this still an issue?

[sruetzler]

In node 6.10.3 this is still not working

[targos]

Yes, this is still an issue, but we cannot fix it directly in Node

[apapirovski]

@nodejs/v8 Anyone know what could be done to resolve this issue? If anything? Seems like it's partially a spec problem but it's important to note that other browsers implement this differently.

[hashseed]

The spec seems pretty clear on this one and hinges on LocalTZA. You could use Date.prototype.setUTCSeconds to work around this problem.