You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have an application with several workers. The primary worker receives HTTP requests and puts data into the queue. The secondary worker consumes messages from the queue and performs the actual job.
If we run all workers with the single wrangler dev command with multiple config flags, everything works as expected, but the Node debugger can listen only to the primary worker. And it makes debugging almost useless because the internal worker does the actual work.
It's possible to run workers separately. Binging services are connected, but it looks like the queue is not. Messages are not consumed.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We have an application with several workers. The primary worker receives HTTP requests and puts data into the queue. The secondary worker consumes messages from the queue and performs the actual job.
If we run all workers with the single
wrangler devcommand with multiple config flags, everything works as expected, but the Node debugger can listen only to the primary worker. And it makes debugging almost useless because the internal worker does the actual work.It's possible to run workers separately. Binging services are connected, but it looks like the queue is not. Messages are not consumed.
I found the https://developers.cloudflare.com/workers/vite-plugin/reference/debugging/ documentation, but I didn't try it because we have a pure backend application, and Vite seems like overkill.
What is the way to debug secondary workers?
Beta Was this translation helpful? Give feedback.
All reactions