the unix timestamp didnt not pick up the timezone change correctly #1159

jianwenl · 2020-10-21T00:34:59Z

Describe the bug
How to get the correct time stamp with a time on a specific timezone ?
I want to check the unix timestamp for 10/15/2020 12:30 PM at Denver, but neither of the approaches (3 and 4) works.

//Los Angeles (correct)
console.log("local notz:", dayjs("10/15/2020 12:30 PM").unix().toString());
// local notz:1602790200
2.
//Los Angeles (wrong)
console.log("local:", dayjs.tz("10/15/2020 12:30 PM").unix().toString());
// local: 1602815400
3.
// Denver (wrong)
console.log(
"denver:",
dayjs.tz("10/15/2020 12:30 PM", "America/Denver").unix().toString()
);
//denver: 1602811800
4.
// Denver (wrong)
console.log(
"denver sep:",
dayjs("10/15/2020 12:30 PM").tz("America/Denver").unix().toString()
);
//denver sep: 1602790200

Expected behavior
A clear and concise description of what you expected to happen.

1.1602790200
2.1602790200
3.1602793800
4.1602793800

Information

Day.js Version [e.g. v1.9.3]
OS: [e.g. macOS 10.15.7]
Browser [e.g. chrome 86]
Time zone: [e.g. GMT-07:00 DST (Pacific Daylight Time)]

iamkun · 2020-10-21T02:44:39Z

You can use dayjs.tz('2020/10/15 10:30', 'America/Denver').unix() to get the correct result 1602779400 at this moment.

We will support custom format parsing in dayjs.tz in a short time.

jianwenl · 2020-10-21T02:51:07Z

10:30

Did you mean 11:30 am for my current time at LA timezone to indicate 12:30pm at Denver ? Is there anyway to calculate this 1 hour difference with dayjs or I need to calculate it by my self ? Thank you.

iamkun · 2020-10-21T03:21:08Z

Sorry for the typo, it should be dayjs.tz('2020/10/15 12:30', 'America/Denver').unix() and resulting 1602786600

fix #1159

jianwenl · 2020-10-21T03:33:57Z

Sorry for the typo, it should be dayjs.tz('2020/10/15 12:30', 'America/Denver').unix() and resulting 1602786600

Which this '12:30' refers to ? '12:30 am' or '12:30 pm' ? I tired all '12:30' '12:30 am' '12:30 pm', but they gave me three different timestamps.

iamkun · 2020-10-21T03:36:08Z

it refers to '12:30 am', I think

jianwenl · 2020-10-21T03:38:42Z

it refers to '12:30 am', I think

They are different :
'2020/10/15 12:30' => 1602786600
'2020/10/15 12:30 am' => 1602768600
'2020/10/15 12:30 pm' => 1602811800

iamkun · 2020-10-21T03:42:36Z

As I said above, we only support this format 2020/10/15 12:30 at present. More available parsing option will be available in #1160.

You can treat 2020/10/15 12:30 as 12:30 am and 2020/10/15 24:30 as 12:30 pm in this version.

However, I do think 12:00 am and 12:00 pm should be the same time.

fix #1159

## [1.9.4](v1.9.3...v1.9.4) (2020-10-23) ### Bug Fixes * Add descriptions to types ([#1148](#1148)) ([9a407a1](9a407a1)) * add devHelper plugin ([#1163](#1163)) ([de49dc8](de49dc8)) * Fix Hungarian (hu) locale ([#1112](#1112)) ([ab13754](ab13754)) * fix minMax plugin parsing empty array bug ([#1062](#1062)) ([368108b](368108b)) * update adding/subtracting Duration from Dayjs object ([#1156](#1156)) ([f861aca](f861aca)) * update en-NZ locale to use proper ordinal formatting function ([#1143](#1143)) ([fcdbc58](fcdbc58)) * update localeData plugin type ([#1116](#1116)) ([ee5a4ec](ee5a4ec)) * update timezone plugin to support custom parse format ([#1160](#1160)) ([48cbf31](48cbf31)), closes [#1159](#1159) * update timezone plugin to support keepLocalTime ([#1161](#1161)) ([1d429e5](1d429e5)), closes [#1149](#1149)

iamkun · 2020-10-23T06:48:38Z

🎉 This issue has been resolved in version 1.9.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

## [1.9.4](iamkun/dayjs@v1.9.3...v1.9.4) (2020-10-23) ### Bug Fixes * Add descriptions to types ([#1148](iamkun/dayjs#1148)) ([9a407a1](iamkun/dayjs@9a407a1)) * add devHelper plugin ([#1163](iamkun/dayjs#1163)) ([de49dc8](iamkun/dayjs@de49dc8)) * Fix Hungarian (hu) locale ([#1112](iamkun/dayjs#1112)) ([ab13754](iamkun/dayjs@ab13754)) * fix minMax plugin parsing empty array bug ([#1062](iamkun/dayjs#1062)) ([368108b](iamkun/dayjs@368108b)) * update adding/subtracting Duration from Dayjs object ([#1156](iamkun/dayjs#1156)) ([f861aca](iamkun/dayjs@f861aca)) * update en-NZ locale to use proper ordinal formatting function ([#1143](iamkun/dayjs#1143)) ([fcdbc58](iamkun/dayjs@fcdbc58)) * update localeData plugin type ([#1116](iamkun/dayjs#1116)) ([ee5a4ec](iamkun/dayjs@ee5a4ec)) * update timezone plugin to support custom parse format ([#1160](iamkun/dayjs#1160)) ([48cbf31](iamkun/dayjs@48cbf31)), closes [#1159](iamkun/dayjs#1159) * update timezone plugin to support keepLocalTime ([#1161](iamkun/dayjs#1161)) ([1d429e5](iamkun/dayjs@1d429e5)), closes [#1149](iamkun/dayjs#1149)

## [1.9.4](iamkun/dayjs@v1.9.3...v1.9.4) (2020-10-23) ### Bug Fixes * Add descriptions to types ([#1148](iamkun/dayjs#1148)) ([9a407a1](iamkun/dayjs@9a407a1)) * add devHelper plugin ([#1163](iamkun/dayjs#1163)) ([de49dc8](iamkun/dayjs@de49dc8)) * Fix Hungarian (hu) locale ([#1112](iamkun/dayjs#1112)) ([ab13754](iamkun/dayjs@ab13754)) * fix minMax plugin parsing empty array bug ([#1062](iamkun/dayjs#1062)) ([368108b](iamkun/dayjs@368108b)) * update adding/subtracting Duration from Dayjs object ([#1156](iamkun/dayjs#1156)) ([f861aca](iamkun/dayjs@f861aca)) * update en-NZ locale to use proper ordinal formatting function ([#1143](iamkun/dayjs#1143)) ([fcdbc58](iamkun/dayjs@fcdbc58)) * update localeData plugin type ([#1116](iamkun/dayjs#1116)) ([ee5a4ec](iamkun/dayjs@ee5a4ec)) * update timezone plugin to support custom parse format ([#1160](iamkun/dayjs#1160)) ([48cbf31](iamkun/dayjs@48cbf31)), closes [#1159](iamkun/dayjs#1159) * update timezone plugin to support keepLocalTime ([#1161](iamkun/dayjs#1161)) ([1d429e5](iamkun/dayjs@1d429e5)), closes [#1149](iamkun/dayjs#1149)

iamkun added a commit that referenced this issue Oct 21, 2020

fix: update timezone plugin to support custom prase format

6a8632b

fix #1159

iamkun mentioned this issue Oct 21, 2020

fix: update timezone plugin to support custom parse format #1160

Merged

iamkun added a commit that referenced this issue Oct 21, 2020

fix: update timezone plugin to support custom parse format

f064c3b

fix #1159

iamkun closed this as completed in #1160 Oct 23, 2020

iamkun added a commit that referenced this issue Oct 23, 2020

fix: update timezone plugin to support custom parse format (#1160)

48cbf31

fix #1159

iamkun added the released label Oct 23, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

the unix timestamp didnt not pick up the timezone change correctly #1159

the unix timestamp didnt not pick up the timezone change correctly #1159

jianwenl commented Oct 21, 2020

iamkun commented Oct 21, 2020 •

edited

Loading

jianwenl commented Oct 21, 2020 •

edited

Loading

iamkun commented Oct 21, 2020

jianwenl commented Oct 21, 2020 •

edited

Loading

iamkun commented Oct 21, 2020

jianwenl commented Oct 21, 2020

iamkun commented Oct 21, 2020 •

edited

Loading

iamkun commented Oct 23, 2020

the unix timestamp didnt not pick up the timezone change correctly #1159

the unix timestamp didnt not pick up the timezone change correctly #1159

Comments

jianwenl commented Oct 21, 2020

iamkun commented Oct 21, 2020 • edited Loading

jianwenl commented Oct 21, 2020 • edited Loading

iamkun commented Oct 21, 2020

jianwenl commented Oct 21, 2020 • edited Loading

iamkun commented Oct 21, 2020

jianwenl commented Oct 21, 2020

iamkun commented Oct 21, 2020 • edited Loading

iamkun commented Oct 23, 2020

iamkun commented Oct 21, 2020 •

edited

Loading

jianwenl commented Oct 21, 2020 •

edited

Loading

jianwenl commented Oct 21, 2020 •

edited

Loading

iamkun commented Oct 21, 2020 •

edited

Loading