ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Memcached's protocol parser rejects negative expiration integers with an ERROR response, but the server performs no time-zone conversion for absolute expiration timestamps. When an expiration value exceeds REALTIME_MAXDELTA (30 days), memcached interprets it as a Unix timestamp expressed in UTC seconds since the epoch. A client that calculates this timestamp
Memcached stores expiration values either as a relative offset in seconds or as an absolute Unix timestamp, comparing the stored value against its own system clock. The protocol specification states that absolute times are interpreted as Unix time, but it does not define any timezone conversion or validation mechanism. Because the server clock runs in UTC, a
Goal: maintain uninterrupted repository interactions after a personal access token (PAT) reaches its expiration date without requiring manual re‑entry. Constraint: GitKraken currently does not monitor PAT validity; it only reacts when a push, pull or fetch fails with an authentication error, at which point the user must re‑enter the token. Uncertainty: wheth
Storage Expiration in Appwrite 1.0.0 Appwrite 1.0.0 introduced a new expiresAt field for storage files, allowing automatic deletion after a specified UTC timestamp. This feature is intended to free storage space without manual cleanup. The cleanup mechanism runs hourly on the server, which can delay deletion by up to 60 minutes. Documentation does not state
When designing a caching layer with memcached, the goal is to guarantee that a key expires at the same instant for all application instances, regardless of the time zone in which each client runs. The memcached server interprets an expiration value: numbers below 2 592 000 seconds are treated as a relative TTL (seconds from the current server time), while va
Goal Maintain artifacts for downstream pipelines while respecting the configured expiration period. Constraints & Uncertainty GitLab allows expiration to be set globally, per-pipeline, or per-job. It is unclear whether artifacts referenced by downstream jobs are exempt from the same expiration rules or if they inherit the same policy as the originating j
memcached
gitkraken
appwrite