Use a singleton to store the memory cache in an internal WeakMap for the current request

[jpreynat]

I made the switch from using the ctx property instead of the cf one from the getRequestContext in the getGlobalContext helper while making the memory cache from the middleware accessible to the next request handler.

However, since this change was deployed, we have an increased number of these errors:
Cannot perform I/O on behalf of a different request. I/O objects (such as streams, request/response bodies, and others) created in the context of one request handler cannot be accessed from a different request's handler.

This PR reverts this change, but also switches to use the singleton helper to create the memory cache, that will store the memory cache and makes it accessible in a WeakMap for the current request context.

[argos-ci]

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	👍 Changes approved	8 changed	Jun 24, 2024, 9:06 AM