Jason Mitchell

Thanks for all the info, we'll look into it.

``` const port = process.env.NODE_PORT || 443; ``` Looks like Polly is mounted on the Webpack server running on whatever process.env.NODE_PORT is (or 443). Either change the port to `3000`...

@bejalane are you calling `await polly.stop();` after each test? If so, can you share what is being emitted from the logger?

No immediate plans but we are interested in it.

@stephenh `_id` could be computed at runtime it's just not the implementation today. If there is enough interest, I think we could make the necessary changes but the work involved...

@rahilvora we would always love to have contributions :)

@rodrigogs what version of puppeteer? I know this used to occur on an older version of puppeteer.

I'm able to reproduce this and see that a request is being iniatiated but not captured and responded to by Polly. Since `await page.setRequestInterception(true);` is set puppeteer is waiting to...

More findings: The passthrough request that Polly makes (the one immediately under the timed out request) occurs via `fetch` and the API responds back with an empty body and a...

Do you have a reproduction that doesn't involve a Google request? Have not triaged further and would appreciate any additional information.