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
Release 0.0.29 after H27.72, H27.73, H27.74 and H27.76: every manifest of config/release.json, the exact requirements of polyspec/hyper-server and @polyspec/hyper-client and the locks that npm, Composer and uv wrote hold 0.0.29 (H27.75).
A Node or Python request that changed nothing in a Redis session sets its new expiry without comparing the lock, as phpredis does, so a long request that only reads no longer answers status 500 when its lock expires; tests check a lock that really expires, a killed process, the HTTP servers of the board and a stop and a start of the Redis server (H27.72).
The Redis sessions hold on a primary with replicas: RedisSentinelSessions and the sessionSetup option of App::open let the PHP server keep the session module of phpredis on the primary that Redis Sentinel names, the Node and Python servers follow it through a Sentinel client, and tests kill the primary under the three servers; the connections take TLS and an ACL user, also with Sentinel, and make bench-sessions measures the capacity of one Redis server (H27.73).
The Redis sessions hold on Redis Cluster with their locks: RedisClusterSessions gives the PHP server the protocol of HY-115, which the rediscluster handler of phpredis lacks, and tests run the three servers on a real cluster of three primaries while a slot moves, through lock failures, a renewal, the HTTP servers, a replica that takes over, TLS and an ACL user (H27.74).
Adopt kit 0.0.93, whose ci-setup installs the PHP symbol extractor, so the shared CI pipeline names no language (H27.76).