kalon33
commented
6 years ago I did that a long time ago but that didn't fix my problem
----- Mail original -----
De: "Michael Lorenzen" notifications@github.com À: "HSLdevcom/digitransit-ui" digitransit-ui@noreply.github.com Cc: "Nicolas Derive" kalon33@ubuntu.com, "Mention" mention@noreply.github.com Envoyé: Mardi 6 Mars 2018 10:44:36 Objet: Re: [HSLdevcom/digitransit-ui] [regression] Time(zone?) problems in digitransit-ui (#908)
We managed to get correct times in our digitranist instance (docker) by adding the full moment timezone info to our config.xxx.js file:
timezoneData: 'Europe/Berlin|CET CEST CEMT|-10 -20 -30|01010101010101210101210101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010|-2aFe0 11d0 1iO0 11A0 1o00 11A0 Qrc0 6i00 WM0 1fA0 1cM0 1cM0 1cM0 kL0 Nc0 m10 WM0 1ao0 1cp0 dX0 jz0 Dd0 1io0 17c0 1fA0 1a00 1ehA0 1a00 1cM0 1cM0 1cM0 1cM0 1cM0 1cM0 1cM0 1fA0 1cM0 1cM0 1cM0 1cM0 1cM0 1cM0 1cM0 1cM0 1cM0 1cM0 1cM0 1fA0 1cM0 1cM0 1cM0 1cM0 1cM0 1cM0 1cM0 1cM0 1cM0 1cM0 1fA0 1o00 11A0 1o00 11A0 1o00 11A0 1qM0 WM0 1qM0 WM0 1qM0 11A0 1o00 11A0 1o00 11A0 1qM0 WM0 1qM0 WM0 1qM0 WM0 1qM0 11A0 1o00 11A0 1o00 11A0 1qM0 WM0 1qM0 WM0 1qM0 11A0 1o00 11A0 1o00 11A0 1o00 11A0 1qM0 WM0 1qM0 WM0 1qM0 11A0 1o00 11A0 1o00 11A0 1qM0 WM0 1qM0 WM0 1qM0 11A0 1o00 11A0 1o00 11A0 1o00 11A0 1qM0 WM0 1qM0 WM0 1qM0 11A0 1o00 11A0 1o00 11A0 1qM0 WM0 1qM0 WM0 1qM0 WM0 1qM0 11A0 1o00 11A0 1o00|41e5',
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or mute the thread .
Since approximatively two weeks, I have timing problems in digitransit-ui using master. Indeed, Before when I choosed to leave (or arrive) at 12:00 I had solutions arriving at that time. Now, they are proposed as if I choosed "14:00" as the time, and indeed, if I set time as "10:00", I get solutions for 12:00.
I used to comment timezone arguments in config file and that used to work, but it doesn't seem to work anymore.
Could you fix this?