🐛 BUG: Service binding doesn't connect to worker running locally with environment

[hexium310]

Which Cloudflare product(s) does this pertain to?

Wrangler

What versions are you using?

3.114.1 [Wrangler]

What operating system and version are you using?

Arch Linux on WSL

Please provide a link to a minimal reproduction

https://github.com/hexium310/wrangler-service-binding-environment-repro

Describe the Bug

Service binding from a worker (worker_a) to another worker (worker_b) running locally with an environment doesn't connect, and using the same/other environment as worker_b in worker_a doesn't either. It has no problem connecting to worker_b without an environment.

Steps to reproduce

1. Clone the above link and pnpm install.
2. Launch worker_b with environment

pnpm exec wrangler --env development -c wrangler.worker_b.toml

3. Launch worker_a in other terminal

pnpm exec wrangler -c wrangler.worker_a.toml

2 and 3 are the same in reverse.

Actual behaviour

connection fails

Expected behaviour

connection succeeds

Please provide any relevant error logs

No response

[emily-shen]

Thanks for the repro! Can confirm I can reproduce this. To get around this, it seems you can get things to work if you run everything in one local dev session (npx wrangler dev -c wrangler.worker_a.toml -c wrangler.worker_b.toml --env development), but you'd have to have the same environment name for both workers.

For anyone looking at this trying to fix it, maybe something to do with how we add the environment name as a suffix to a worker name? and that's forgotten somewhere...?

[hexium310]

I tried to check running multiple workers at once with one command using [vars], and it seems that wrangler dev -c wrangler.worker_a.toml -c wrangler.worker_b.toml --env development ignores an environment of worker_b.

[emily-shen]

Sorry about that, turns out the flag only applies to the first worker.

If you append the environment name to the service name (rather than using the environment key), you can then run each worker separately and they should connect.

# in wrangler.worker_a.toml
services = [
  { binding = "WORKER_B", service = "worker_b"},
]
env.development.services = [
  { binding = "WORKER_B", service = "worker_b-development"},
]

(you don't need to change the name in wrangler.worker_b.toml)

I don't think this is documented anywhere, so i'll leave this ticket open while I document this behaviour - thanks for reporting 🧡

[hexium310]

I have confirmed that it works that way. Thank you.

[emily-shen]

docs here cloudflare/cloudflare-docs#20873

[smaldd14]

I came across this issue during research of a similar issue I am having.

I have a worker using browser rendering, and a workflow that I am trying to develop to connect to this worker.

Browser rendering requires --remote flag, and workflows does not support --remote.

Does this mean that I cannot connect to the browser rendering worker when trying to develop my workflow locally?