Hello,
[Technical]
The bug was introduced in commit:
commit e0ff769e1980f19486843da7ded91ab9f613a58e
Date: Wed Sep 23 12:33:53 2015 -0400
history: fix time calculation
We worked with periods of 24 consecutive hours to define 'Today',
'Yesterday'... (c.f: https://en.wikipedia.org/wiki/Nychthemeron)
This was misleading for the user.
We now integrate with the local system time to define these terms.
Issue: #76563
Change-Id: Ifc642499dbcfd050cce8e3b05acec15dc639fb38
The previous algorithm was using lower level APIs and less prone to integer
underflow and negative array indices.
I am working on restoring the previous algorithm (without the Nychthemeron).
I also found the previous code had an issue with timezone on December 31.
This could not cause a crash, but better fix it now instead of forgetting
about it. It simply cause the calls from December 31 to be classified as
December 30.
Anyhow, the patch will be in the validation pipeline in a few minutes and
will be in the nightly once someone else merge it.
Happy new year,
Emmanuel
----- Original Message -----
From: "Baptiste Jonglez" <bapti...@bitsofnetworks.org>
To: ring@lists.savoirfairelinux.net
Sent: Friday, January 1, 2016 4:40:06 PM
Subject: Re: [Ring] Unlaunchable after Ubuntu 14.04 nightly update
This is a bug related to the change of year :)
A patch is available at https://tuleap.ring.cx/plugins/tracker/?aid=213
On Fri, Jan 01, 2016 at 01:09:51PM -0800, Martin Hill wrote:
> After today's update - Ring will not launch. This the case with 2 different
> machines - Happy new Year :-)
> _______________________________________________
> Ring mailing list
> Ring@lists.savoirfairelinux.net
> https://lists.savoirfairelinux.net/mailman/listinfo/ring
_______________________________________________
Ring mailing list
Ring@lists.savoirfairelinux.net
https://lists.savoirfairelinux.net/mailman/listinfo/ring
_______________________________________________
Ring mailing list
Ring@lists.savoirfairelinux.net
https://lists.savoirfairelinux.net/mailman/listinfo/ring
