7 replies

Several questions about developing locally with queues

1. The Get started guide for queues suggests running

wrangler tail

wrangler tail

to watch published messages arrive. However this gives an error 10007 when working locally. Should this command work locally?
2. How does one configure the batch size/frequency of a queue when working locally, since the queue is automatically-created by Wrangler? That is, you don't run the

create

create

command when working locally, nor do you bind the queue explicitly to your config TOML/JSON.
3. In my consumer handler, I have:

async queue(batch, env) {
    for (const message of batch.messages)
        console.log('RECEIVED!', message.body);
}

async queue(batch, env) {
    for (const message of batch.messages)
        console.log('RECEIVED!', message.body);
}

Note I'm not running

message.ack()

message.ack()

. I expected that this would result in the consumer repeatedly re-receiving the same message (because I never acknowledged it). But this doesn't happen; the console message shows up only once. Am I mistaken here? Or is this just a quick of local development queue simulation?
4. Is there any ETA on queues being supported with the

--remote

--remote

flag? This would make life MUCH easier - right now developing with queues is really quite painful.

Thank you in advance.

Several questions about developing locally with queues

Similar Threads

Similar Threads

Similar Threads