@luvio/environments 0.69.0 → 0.70.0

package/dist/es/es2018/environments.js

@@ -375,9 +375,6 @@ function isStoreEntryError(storeRecord) {
     return storeRecord.__type === 'error';
 }
 
-function isStoreEntryExpiredAndError(storeRecord, expirationTimestamp, now) {
-    return isStoreEntryError(storeRecord) && expirationTimestamp < now;
-}
 /**
  * Takes a set of entries from DurableStore and publishes them via the passed in funcs.
  * This respects expiration and checks for valid DurableStore data shapes.  This should
@@ -400,7 +397,6 @@ function publishDurableStoreEntries(durableRecords, publish, publishMetadata) {
         // no records to revive
         return { revivedKeys, hadUnexpectedShape };
     }
-    const now = Date.now();
     for (let i = 0, len = durableKeys.length; i < len; i += 1) {
         const key = durableKeys[i];
         const durableRecord = durableRecords[key];
@@ -416,27 +412,12 @@ function publishDurableStoreEntries(durableRecords, publish, publishMetadata) {
             continue;
         }
         if (metadata !== undefined) {
-            const { expirationTimestamp, staleTimestamp } = metadata;
+            const { expirationTimestamp } = metadata;
             if (expirationTimestamp === undefined) {
                 // if unexpected expiration data skip reviving
                 hadUnexpectedShape = true;
                 continue;
             }
-            // if past stale TTL then don't revive
-            if (staleTimestamp !== undefined && staleTimestamp < now) {
-                continue;
-            }
-            // We don't want to revive a cached value if it's an error and it's
-            // expirationTimestamp TTL is expired, otherwise we would never hit the network
-            // during resolveSnapshot or rebuildSnapshot because the way the Reader works.
-            // If a StoreEntry is an error, the Reader will return UnfulfilledSnapshot
-            // if stale TTL is expired.  But it will return ErrorSnapshot (instead of
-            // StaleSnapshot) if expirationTimestamp TTL is expired (but stale TTL isn't).
-            // In our environment the stale TTL is maxed out so Reader will always
-            // return ErrorSnapshot.
-            if (isStoreEntryExpiredAndError(data, expirationTimestamp, now)) {
-                continue;
-            }
             publishMetadata(key, metadata);
         }
         if (isStoreEntryError(data)) {

package/dist/umd/es2018/environments.js

@@ -379,9 +379,6 @@
         return storeRecord.__type === 'error';
     }
 
-    function isStoreEntryExpiredAndError(storeRecord, expirationTimestamp, now) {
-        return isStoreEntryError(storeRecord) && expirationTimestamp < now;
-    }
     /**
      * Takes a set of entries from DurableStore and publishes them via the passed in funcs.
      * This respects expiration and checks for valid DurableStore data shapes.  This should
@@ -404,7 +401,6 @@
             // no records to revive
             return { revivedKeys, hadUnexpectedShape };
         }
-        const now = Date.now();
         for (let i = 0, len = durableKeys.length; i < len; i += 1) {
             const key = durableKeys[i];
             const durableRecord = durableRecords[key];
@@ -420,27 +416,12 @@
                 continue;
             }
             if (metadata !== undefined) {
-                const { expirationTimestamp, staleTimestamp } = metadata;
+                const { expirationTimestamp } = metadata;
                 if (expirationTimestamp === undefined) {
                     // if unexpected expiration data skip reviving
                     hadUnexpectedShape = true;
                     continue;
                 }
-                // if past stale TTL then don't revive
-                if (staleTimestamp !== undefined && staleTimestamp < now) {
-                    continue;
-                }
-                // We don't want to revive a cached value if it's an error and it's
-                // expirationTimestamp TTL is expired, otherwise we would never hit the network
-                // during resolveSnapshot or rebuildSnapshot because the way the Reader works.
-                // If a StoreEntry is an error, the Reader will return UnfulfilledSnapshot
-                // if stale TTL is expired.  But it will return ErrorSnapshot (instead of
-                // StaleSnapshot) if expirationTimestamp TTL is expired (but stale TTL isn't).
-                // In our environment the stale TTL is maxed out so Reader will always
-                // return ErrorSnapshot.
-                if (isStoreEntryExpiredAndError(data, expirationTimestamp, now)) {
-                    continue;
-                }
                 publishMetadata(key, metadata);
             }
             if (isStoreEntryError(data)) {

package/dist/umd/es5/environments.js

@@ -414,9 +414,6 @@
         return storeRecord.__type === 'error';
     }
 
-    function isStoreEntryExpiredAndError(storeRecord, expirationTimestamp, now) {
-        return isStoreEntryError(storeRecord) && expirationTimestamp < now;
-    }
     /**
      * Takes a set of entries from DurableStore and publishes them via the passed in funcs.
      * This respects expiration and checks for valid DurableStore data shapes.  This should
@@ -439,7 +436,6 @@
             // no records to revive
             return { revivedKeys: revivedKeys, hadUnexpectedShape: hadUnexpectedShape };
         }
-        var now = Date.now();
         for (var i = 0, len = durableKeys.length; i < len; i += 1) {
             var key = durableKeys[i];
             var durableRecord = durableRecords[key];
@@ -455,27 +451,12 @@
                 continue;
             }
             if (metadata !== undefined) {
-                var expirationTimestamp = metadata.expirationTimestamp, staleTimestamp = metadata.staleTimestamp;
+                var expirationTimestamp = metadata.expirationTimestamp;
                 if (expirationTimestamp === undefined) {
                     // if unexpected expiration data skip reviving
                     hadUnexpectedShape = true;
                     continue;
                 }
-                // if past stale TTL then don't revive
-                if (staleTimestamp !== undefined && staleTimestamp < now) {
-                    continue;
-                }
-                // We don't want to revive a cached value if it's an error and it's
-                // expirationTimestamp TTL is expired, otherwise we would never hit the network
-                // during resolveSnapshot or rebuildSnapshot because the way the Reader works.
-                // If a StoreEntry is an error, the Reader will return UnfulfilledSnapshot
-                // if stale TTL is expired.  But it will return ErrorSnapshot (instead of
-                // StaleSnapshot) if expirationTimestamp TTL is expired (but stale TTL isn't).
-                // In our environment the stale TTL is maxed out so Reader will always
-                // return ErrorSnapshot.
-                if (isStoreEntryExpiredAndError(data, expirationTimestamp, now)) {
-                    continue;
-                }
                 publishMetadata(key, metadata);
             }
             if (isStoreEntryError(data)) {

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@luvio/environments",
-    "version": "0.69.0",
+    "version": "0.70.0",
     "description": "Luvio Environments",
     "main": "dist/umd/es2018/environments.js",
     "module": "dist/es/es2018/environments.js",
@@ -26,6 +26,6 @@
         "dist/"
     ],
     "dependencies": {
-        "@luvio/engine": "0.69.0"
+        "@luvio/engine": "0.70.0"
     }
 }