Sean Feldman

Looks like `response-packet-size` could do the trick. Thank you, @xyh1.

> MOQ has had some very werid behavior. Elaborate?

Looks like the workaround we've discussed is going to be materialized as an official Docker image, released with every update to the NPM package (https://github.com/firebase/firebase-tools/issues/1644). Which is a welcomed change...

The entry point in the image must run the following command. ```bash firebase emulators:start --project PROJECT_ID ``` To avoid hardcoding `PROJECT_ID` it would need to be passed to the container...

It would be great to know what's the status of https://github.com/firebase/firebase-tools/issues/1644 and the associated PR https://github.com/firebase/firebase-tools/pull/6255 before this issue can be closed or anything is done.

Yes, @jskeet.

@yvgopal, this was a standard namespace. I'll refer a client of mine to this issue and ask them to raise a support case referencing this issue.

@asos-richardevans, could you share the method used to create the entities (ARM/Bicep, Terraform, Management SDK, other SDK, etc.)? When using the old SDK (track 0) to create the entities and...

While I understand the suggestion to treat entity listing as a resource operation and use a separate library, there are several scenarios when using a single library to perform operations...

This already exists (to an extent) with Azure Service Bus when you create a queue or a topic name with the path delimited by "/".