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
What is happening is that permanent subscriptions created before 1.13.0 are using the first one, so now the following checking in Subscription::toJson():
if (this->expires != PERMANENT_EXPIRES_DATETIME)
{
jh.addDate("expires", this->expires);
}
is failing and activates the jh.addDate() even when subscription is permanent, so causing the crash (add addDate calls internally gmtime() with so large value and fails).
The text was updated successfully, but these errors were encountered:
A bug was introduced by 1a49367 in PR #3084 around January 22nd, 2018 as part of issue #3004 implementation, in the 1.13.0 development cycle.
In particular the bug is due to this change:
where:
What is happening is that permanent subscriptions created before 1.13.0 are using the first one, so now the following checking in Subscription::toJson():
is failing and activates the jh.addDate() even when subscription is permanent, so causing the crash (add addDate calls internally gmtime() with so large value and fails).
The text was updated successfully, but these errors were encountered: