Cloudflare

no that's what i'm saying, it's the inverse of that

```ts
setInterval(() => console.log(Date.now(), 1000));
```

in local, this always prints the same date

in dev and experimental-local, this prints a new date every time

local's Spectre mitigations vs production's Spectre mitigations are just a discrepancy between the environments

That isn't a 'real' 1000ms - it's 1000ms aligned with a 'fake' clock

You can do `Date.now()`, do some hard compute that takes a few seconds, `Date.now()` and end up with a delta of 7ms - or 150ms - or 900ms - who knows, it varies

ah, so you're saying that even when it's "working" (i.e. unfrozen), it's still fuzzed, with some delta

Yeah - it's 'accurate' enough for vague timing, or rudimentary tracing, but never enough for you to use for a Spectre attack that requires repeated timing with sub-ms accuracy

understood. i am 100% fine with that limitation, it shouldn't impact my use-case at all

so, just to wrap things up then, the fact that `Date.now()` is completely frozen  in `--local` — not just fuzzed, but literally unchanging EVER until the worker is restarted — is presumed to be a bug in the miniflare that `local` uses?

fuzzing the time i completely understand, given Spectre. freezing i just don't get.

current time in local only advances on external I/O - like reaching into cache, or making a fetch subrequest

whereas current time in production advances on any async work really - like the `scheduler.wait` or `interval` stuff

ref: https://github.com/cloudflare/miniflare/commit/a50b9687507d54055c5ec40963d2524280167116

but yeah I'd consider that a discrepancy between `local` and the expected behaviour

but I also have no documentation or references to guarantee that one day `scheduler.wait(1)` won't stop advancing the clock

1) i'm going to try doing some explicit disk I/O in the setInterval, to validate

2) where do i pass `--actual-time`? it's not recognized as a flag in `wrangler dev`

It's a Miniflare only flag - and despite `wrangler dev --local` spawning Miniflare in the background, I don't think you can actually pass it w/ wrangler dev

Someone might correct me on that, I've never used it

can i not call `fs.writeFileSync` in a worker? just trying to 'force' I/O to test the theory

It depends what you're trying to test - a simple `fetch("https://google.com")` would update the time