镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

date.toString timezone differences in v10.4.x #21390

Description

@ravishivt
  • Version: v10.4.1
  • Platform: Linux 8a47e98f5019 4.9.87-linuxkit-aufs deps: update openssl to 1.0.1j #1 SMP Wed Mar 14 15:12:16 UTC 2018 x86_64 Linux (docker node:10.4.1-alpine container)
  • Subsystem: unknown

v10.4.0 does not abbreviate the timezone. I think this is due to the V8 6.6 -> 6.7 upgrade in #19989 as per this comment but wanted to confirm this is the correct behavior. The change has affected many of my jest snapshots.

v10.3.0:

# node -e 'console.log((new Date(0)).toString())'
Thu Jan 01 1970 00:00:00 GMT+0000 (UTC)

v10.4.1 (and v10.4.0):

# node -e 'console.log((new Date(0)).toString())'
Thu Jan 01 1970 00:00:00 GMT+0000 (Coordinated Universal Time)

Activity

  1. ravishivt commented on Jun 18, 2018

    @ravishivt
    Author

    I found https://bugs.chromium.org/p/v8/issues/detail?id=6076#c10 which indicates V8 did make this change on purpose. Closing this since this is now expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    v8 engineIssues and PRs related to the V8 dependency.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions