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
{{ message }}
Repository navigation
ClusterReplication drivers are saving erroneous expiration date in low-level backends #855
The ClusterFullReplication and ClusterSemiReplication are saving erroneous expiration date in low-level backends. The saved date is a now date, not a now + "defaultTtl" date
changed the title [-]ClusterFullReplication and ClusterSemiReplication are saving erroneous expiration date in low-level backends[/-][+]ClusterReplication drivers are saving erroneous expiration date in low-level backends[/+]on Mar 30, 2022
Activity
github-actions commentedon Mar 29, 2022
Hello curious contributor !
Since it seems to be your first contribution, make sure that you've been:
If everything looks unclear to you, tell us what 😄
The Phpfastcache Team
Geolim4 commentedon Mar 29, 2022
Stupid bot, who the hell coded you ?
Fixed #855
Fixed #855
Added tests for #855
Fixed #855 (v8)
Fixed #855 (v8)
[-]ClusterFullReplication and ClusterSemiReplication are saving erroneous expiration date in low-level backends[/-][+]ClusterReplication drivers are saving erroneous expiration date in low-level backends[/+]Geolim4 commentedon Mar 30, 2022
Will be fixed in 8.1 and 9.1.
The
9.1release will immediately follow the9.0.2.