Closed kitsonk closed 1 year ago
Hello,
We have identified the cause to be a recent backward-incompatible change in the KV system. It caused written values from remote clients to incorrectly have an expiration time of zero. We are working on a fix.
Projects on Deno Deploy are not affected.
Thanks for the update. For my use case it is really impossible to work around, as the source data requires source data from outside the deploy deployment. Hopefully it is a quick fix.
A fix has been deployed. @kitsonk could you try it again?
@losfair thank you, it appears to be resolved.
🔍
Type of feedback
Bug report
Description
Attempting to upload data remotely, the data appears briefly in dash.deno.com but then disappears after a bit, making it unavailable for the application.
Steps to reproduce (if applicable)
deno task build docs -p
from ts-why/tswhyExpected behavior (if applicable)
Values persisted to Deno KV do not disappear. This is what occurs locally with Deno CLI.
Possible solution (if applicable)
No response
Additional context
No response