Has anyone seen a case where bindings to D1 or DO don't work when running wrangler with --test-sched
Has anyone seen a case where bindings to D1 or DO don't work when running wrangler with --test-scheduled flag? I get silent failures when trying to access D1 or D0 in either case, only locally with cron tasks on a worker. But the same worker codebase runs fine with the bindings when I run it as a regular worker for both fetch or queue incoming requests.
I've tested this at its most raw level. When I run the cron task locally, it starts fine, runs fine until I use either binding. Even for a basic statement such as:
await env.BINDING.exec("select * from users");
Fails silently with or without debugging on. I tested, and the --persist-to is set correctly, where I have a shared folder for D1/DO storage.
Again, this worker access all bindings fine running under the queue/fetch context, just not when running --test-scheduled
I've tested this at its most raw level. When I run the cron task locally, it starts fine, runs fine until I use either binding. Even for a basic statement such as:
await env.BINDING.exec("select * from users");
Fails silently with or without debugging on. I tested, and the --persist-to is set correctly, where I have a shared folder for D1/DO storage.
Again, this worker access all bindings fine running under the queue/fetch context, just not when running --test-scheduled
