Greg Baker

Miniflare appears to automatically set the `Sec-WebSocket-Protocol` response header to match the `Sec-WebSocket-Protocol` request header (while CF Worker does not). This test appears to assert this behavior https://github.com/cloudflare/miniflare/blob/92d98c9ac8636853dfb266f3ac5013fd3858d52b/packages/web-sockets/test/fetch.spec.ts#L86 When we...

Thanks @mrbbot. Thanks for the suggested workaround, that is exactly what we are doing for now.

Today developers can wrap these functions with error handling themselves before passing them as options to replicache. This could work reasonably well for the error reporting (e.g. Sentry) or even...

Plan to investigate this more today. @koahmad Can you share the details of your local dev setup?

@koahmad thanks, that is enough to help me get started on reproing.

More information on this. Another of our customers reports they see this error in their error reporting from prod. The browser breakdown is   Errors from one session: 

This can happen in production when 1. the idb is deleted a. via code b. via devtools c. or by the browser due to hitting size quota 2. close is...

Wanted to share an update on our current understanding of the impact of this bug when it occurs in production. If the client view is < 100MBs in size the...

Ok I think we now have a solid plan for addressing this: 1. When this error happens (and the Replicache instance hasn't been closed) try to reopen the connection to...

> I think eventually there should also be a (5) which is a bigger project: > > * some sort of first-class feature around managing quota and eviction. Agree, though...