What type of validation (if any) is done against the parameters of an RPC call (on the sending and r
What type of validation (if any) is done against the parameters of an RPC call (on the sending and receiving side)?
wrangler dev?Users can review the execution history of their Cron Triggers in Past Cron Events under Logs ↗ but I don't see "Past Cron Events" anywhere for my worker
cacheTtl in cf object in the fetch request, but it doesn't seem to do anything, which I assume is due to it being a POST request (CF-Cache-Status always returns DYNAMIC for this response).
There have been no events in the past week. which is not true, but I assume if I just give it some time something will show up?
walshy@workers/observability/telemetry/keys__dirname and __filename. Those variables are from the global scope and I didn't achieve to mock them though the [alias] feature of the wrangler.toml.[define]? That is for global variable substitution.
define accept a Record<string, string>.__dirname. I tried to set it like the following:error: Invalid define value (must be an entity name or valid JSON syntax): ./__dirname is not happy: The "path" argument must be of type string. Received an instance of Object


{
"success": false,
"messages": [],
"errors": [
{
"code": 10104,
"message": "workers_observability.api.error.authentication.no_access_to_workers_observability"
}
],
"result": null
}[define]
__dirname = "./"[define]
__dirname = "{'foo': 'bar'}"