In-Memory Durable Objects #391
Conversation
Deploying with
|
| Latest commit: |
4df6f54
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d98ab532.cf-miniflare.pages.dev |
| Branch Preview URL: | https://tre-durable-objects.cf-miniflare.pages.dev |
| (now.getMonth() + 1).toString().padStart(2, "0"), | ||
| now.getDate().toString().padStart(2, "0"), | ||
| ].join("-"); | ||
| const FALLBACK_COMPATIBILITY_DATE = "2000-01-01"; |
There was a problem hiding this comment.
Why are we shifting from today to a compat date of 2000? Surely keeping it up to date would be better?
There was a problem hiding this comment.
The runtime has a maximum compatibility date it supports, which may lag behind the current date by a few days. If we specify a date after this, it will throw an error. I think the default compatibility date (at least for Miniflare) should be fixed in the past too, and shouldn't depend on the current time.
There was a problem hiding this comment.
Sure, that makes sense. Do we not want something slightly more recent than 2000 though?
There was a problem hiding this comment.
At least after the last behaviour change, which looks like it was 2022-08-04 https://developers.cloudflare.com/workers/platform/compatibility-dates/
This PR adds support for non-durable Durable Objects. The open-source runtime does not yet support persisted objects. Data is lost when calling
setOptions()or restarting. Closes #366.