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
moment-timezone has a slightly weird behavior for dates right at the edge of a DST switch. If a time zone is explicitly set using setDefault, it's behaving differently even if the time zone is set to the one returned by guess:
Execute on a computer which is set to german time zone:
moment-timezone
has a slightly weird behavior for dates right at the edge of a DST switch. If a time zone is explicitly set usingsetDefault
, it's behaving differently even if the time zone is set to the one returned byguess
:Execute on a computer which is set to german time zone:
This can cause issues in two situations:
kibana/packages/kbn-es-query/src/utils.ts
Line 14 in 202980e
kibana/src/plugins/data/common/search/aggs/buckets/date_range.ts
Line 98 in b140cb5
kibana/src/plugins/data/common/search/aggs/buckets/date_histogram.ts
Line 139 in 3c0e5e5
kibana/src/plugins/vis_types/timeseries/server/lib/vis_data/response_processors/series/time_shift.js
Line 31 in c51565b
To disambiguate these cases, I propose to always set the default timezone to the guessed one
kibana/src/core/public/integrations/moment/moment_service.ts
Line 29 in 4584a8b
The text was updated successfully, but these errors were encountered: