waitUntil is technically available as a member of the first arg to the DO constructor
waitUntil
H
LH
GHGG
GGH
locationHint. I can do a manually mapping from colos to regions, but iirc, they aren't 100% stable yet.GL
./durable-objects at the same level as ./functions in my repo. Put the wrangler.toml file for the Worker/DO in the ./durable-objects folder and run wrangler publish from that folder whenever you update. I'm constantly forgetting that step and wondering why my smoke tests fail though so I keep promising myself I'm going to automate the publish as part of my Pages build but I have yet to do it.
BLLwrangler pages dev
Z
U
D
logger.Drain() looking like:draining logs! log, but not the done! log. I've also tried returning the googleDestinationFunction log directly (which also contains logs that I do not see) and it just seems like the DO is exiting once the promise starts running... It is my understanding that the DO should let any other promises run the in background, correct?Hworkers_dev route, so the Worker itself cannot incur any Requests.Hwrangler.tomlexport class MyDOClass, but if it doesn't just add the export default {}.Hwranglerwrangler devwrangler pages dev dist --do BINDING=MyDOClass, they should be able to link together...UlocationHint./durable-objects./durable-objects./functionswrangler publish86400 seconds x 128 MB = 11059200
11059200 / 1000 (1GB) = 11059.2
11059.2 x 30 (30 days) = 331776
331776 / 1000000 (million) = 0.331776
0.331776 x $12.50 = $4.1472const res = new Response("broadcasted")
logger.Drain()
return reslogger.Drain()async (lines) => {
console.log("draining logs!")
await googleDestinationFunction(lines, c.env)
console.log("done!")
}draining logs!done!googleDestinationFunctionworkers_devexport class MyDOClassexport default {}wrangler pages dev dist --do BINDING=MyDOClass