ioredis-toolkit 0.0.6 → 0.0.8

package/dist/client.js

@@ -295,6 +295,7 @@ export class RedisClientWrapper {
                 revocationStore: options.revocationStore ?? this.revocationStore,
             };
             this._session = createSessionManager(params);
+            void this._session.init();
             this.config.sessionOptions = params;
         }
         return this._session;

package/dist/session/scripts/create.lua

@@ -1,7 +1,8 @@
 -- create.lua (version 1)
 -- Atomically creates a session record, registers it in the user index
--- (ZSET, score = createdAt), optionally claims an idempotency key, and
--- enforces maxSessionsPerUser with bounded oldest-first eviction.
+-- (ZSET, score = microsecond-resolution Redis server time, used purely
+-- for eviction ordering - see below), optionally claims an idempotency
+-- key, and enforces maxSessionsPerUser with bounded oldest-first eviction.
 --
 -- KEYS[1] = session record key
 -- KEYS[2] = user session index key (ZSET)
@@ -44,7 +45,21 @@ if redis.call('EXISTS', key) == 1 then
 end
 
 redis.call('SET', key, ARGV[1], 'EX', tonumber(ARGV[4]))
-redis.call('ZADD', index, tonumber(ARGV[3]), ARGV[2])
+
+-- The user index score is used purely for oldest-first eviction ordering
+-- (never as the record's createdAt, which is app-stamped seconds inside the
+-- envelope). Redis breaks equal ZSET scores by lexicographic member order,
+-- not insertion order, so scoring by second-granularity createdAt would
+-- make eviction pick an arbitrary (jti-lexicographic) session rather than
+-- the actual oldest one whenever a user creates more than one session in
+-- the same wall-clock second - a realistic case under normal traffic, not
+-- just a burst edge case. Redis is single-threaded, so two scripts touching
+-- the same user slot never observe the same TIME() reading in practice;
+-- microsecond-resolution server time therefore gives a strictly monotonic,
+-- clock-skew-free ordering key for this user's index.
+local t = redis.call('TIME')
+local orderScore = tonumber(t[1]) + (tonumber(t[2]) / 1000000)
+redis.call('ZADD', index, orderScore, ARGV[2])
 
 local evicted = {}
 local limit = tonumber(ARGV[5])

package/dist/session/scripts/rotate-encrypted.lua

@@ -37,7 +37,8 @@ if env.v ~= 2 then
   return 6
 end
 
-local now = tonumber(redis.call('TIME')[1])
+local t = redis.call('TIME')
+local now = tonumber(t[1])
 
 -- Retry-safe replay detection BEFORE rejecting consumed records.
 -- The rotation nonce uniquely identifies the rotation: when the consumed
@@ -102,6 +103,8 @@ end
 
 redis.call('SET', KEYS[2], cjson.encode(nextEnv), 'EX', nextTtl)
 redis.call('ZREM', KEYS[3], ARGV[7])
-redis.call('ZADD', KEYS[3], now, ARGV[3])
+-- Microsecond-resolution ordering score - see create.lua for why
+-- second-granularity scores break oldest-first eviction ordering.
+redis.call('ZADD', KEYS[3], tonumber(t[1]) + (tonumber(t[2]) / 1000000), ARGV[3])
 
 return { 1, ARGV[3] }

package/dist/session/scripts/rotate.lua

@@ -44,7 +44,8 @@ if env.v ~= 1 then
 end
 
 local s = env.s
-local now = tonumber(redis.call('TIME')[1])
+local t = redis.call('TIME')
+local now = tonumber(t[1])
 
 -- Retry-safe replay detection BEFORE rejecting consumed records.
 -- The rotation nonce uniquely identifies the rotation: when the consumed
@@ -114,6 +115,8 @@ end
 
 redis.call('SET', KEYS[2], cjson.encode(nextEnv), 'EX', nextTtl)
 redis.call('ZREM', KEYS[3], ARGV[6])
-redis.call('ZADD', KEYS[3], now, ARGV[2])
+-- Microsecond-resolution ordering score - see create.lua for why
+-- second-granularity scores break oldest-first eviction ordering.
+redis.call('ZADD', KEYS[3], tonumber(t[1]) + (tonumber(t[2]) / 1000000), ARGV[2])
 
 return { 1, ARGV[2] }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ioredis-toolkit",
-  "version": "0.0.6",
+  "version": "0.0.8",
   "description": "Production-grade, type-safe Redis infrastructure for standalone, Sentinel, and Cluster deployments",
   "type": "module",
   "main": "./dist/index.js",