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
Deal with TTL exception for templateScene, whereby expireAt is not set in the mongo document (what actually enforces expiry behavior in mongodb). Perhaps via flags where persist: true, ttl: n are set, but some new flag (retainTTL: true ?) does same bypass of expireAt so every time someone loads the scene from persist (or instantiates a sceneTemplate), the object is kept with a "fresh" TTL
Even worse wiith the ugly workaround to keep a Set of expirations, this should be redone to better handle time in an absolute manner, something previously avoided because of the lack of time sync.
Splitting this one one off
Deal with TTL exception for templateScene, whereby expireAt is not set in the mongo document (what actually enforces expiry behavior in mongodb). Perhaps via flags where persist: true, ttl: n are set, but some new flag (retainTTL: true ?) does same bypass of expireAt so every time someone loads the scene from persist (or instantiates a sceneTemplate), the object is kept with a "fresh" TTL
Originally posted by @hiliang-cmu in #4 (comment)
The text was updated successfully, but these errors were encountered: