chigan (iPad Pro)
On Jun 3, 2019, at 5:39 PM, Rod Yager
mailto:r...@yager.net.au>> wrote:
Dear Leon,
Thanks for all your work on this. This works as well as we are going to be able
to manage unless and until WU fixes the bug.
The remaining issue affects just one date, the “change-over”
799
date_epoch_utc: 2019-05-29 03:59:59 tz: America/New_York obsTimeUtc:
2019-05-29T03:59:59Z obsTimeLocal: 2019-05-28 23:59:59
Number of WU records: 288
Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
On May 29, 2019, at 8:53 PM, Rod Yager
mailto:r...@yager.net.au>
you to say that those changes were no good for you at
certain times of the PRESENT day, such as before 10 a.m. your local time, was
it?
Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
On Jun 2, 2019, at 5:50 PM, Rod Yager
mailto:r...@yager.net.au>> wrote:
Well, it turns
teline).
Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
On Jun 1, 2019, at 11:08 PM, Rod Yager
mailto:r...@yager.net.au>> wrote:
Dear Leon,
If WU doesn’t fix their bug, the solution is really quite simple.
We need to make 3 requests to WU for the data: one request for the
ards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
On Jun 1, 2019, at 6:03 PM, Rod Yager
mailto:r...@yager.net.au>> wrote:
Dear Leon,
Your approach is flawed. It won’t work for historical data.
If you run
wunderdates —date=2019-01-01 at 9pm your time you will receive the dat
05-29 03:59:59 tz: America/New_York obsTimeUtc:
2019-05-29T03:59:59Z obsTimeLocal: 2019-05-28 23:59:59
Number of WU records: 288
Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad Pro)
On May 29, 2019, at 8:53 PM, Rod Yager
mailto:r...@yager.net.au>> wrote:
Further to
iscard utc 21:00 - 23:59
or have i not understood correctly?
On Friday, 31 May 2019 05:48:09 UTC+3, Rod Yager wrote:
I constructed a cron job which exectued wunderdates --date=2019-05-30 twice
every hour, once 2 minutes before the hour and once 2 minutes after the hour.
Consistent with my e
Have downloaded the wunderdates.
I am in the UTC+10 timezone.
So far, my experience is that when the current time is between 00:00+10 and
09:59+10 (14:00UTC to 23:59 UTC) (so the local date is one day in advance
of the UTC date), the API fetches data for the local-time day immediately
ks again, and for the reminder. =D
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad Pro)
>
> On May 29, 2019, at 6:14 PM, Rod Yager >
> wrote:
>
> There is definitely a time zone issue. I am in the Sydney Australia
> timezone (UTC +10 hours).
There is definitely a time zone issue. I am in the Sydney Australia
timezone (UTC +10 hours).
It is currently 8am local time on May 30, 2019. (10pm May 29, 2019 UTC)
If I execute
./wunderfixer --verbose --date=2019-05-29 --epsilon=125
I get
Using configuration file
10 matches
Mail list logo
