Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Effect #1834

Open
thewilkybarkid opened this issue Aug 1, 2024 · 0 comments
Open

Use Effect #1834

thewilkybarkid opened this issue Aug 1, 2024 · 0 comments

Comments

@thewilkybarkid
Copy link
Member

No description provided.

thewilkybarkid added a commit that referenced this issue Aug 1, 2024
thewilkybarkid added a commit that referenced this issue Aug 5, 2024
thewilkybarkid added a commit that referenced this issue Aug 5, 2024
thewilkybarkid added a commit that referenced this issue Aug 5, 2024
thewilkybarkid added a commit that referenced this issue Aug 28, 2024
thewilkybarkid added a commit that referenced this issue Aug 28, 2024
CI started failing as there was an unexpected update to fast-check, and local ESLint caches prevented us from seeing the problems in unchanged code.

Refs #1834, 8f6b150
thewilkybarkid added a commit that referenced this issue Aug 28, 2024
CI started failing as there was an unexpected update to fast-check. This version now generates URLs containing '//' as the beginning of the path, which then break's constructing URL objects which consider it to be an invalid protocol relative URL.

Refs #1834, 8f6b150, dubzzz/fast-check#4896
thewilkybarkid added a commit that referenced this issue Aug 29, 2024
thewilkybarkid added a commit that referenced this issue Aug 29, 2024
thewilkybarkid added a commit that referenced this issue Sep 2, 2024
The it-all module seems to be incompatible with Jest's ESM support. I have no idea why, but it's easy enough to replace with Effect.

Refs #1834, #1900
thewilkybarkid added a commit that referenced this issue Sep 4, 2024
thewilkybarkid added a commit that referenced this issue Sep 4, 2024
There's a name collision between the Effect service tag and the IoRedis export; we've decided to alias the latter for the moment, but the collision might become encapsulated.

Refs #1834
erkannt added a commit that referenced this issue Sep 4, 2024
thewilkybarkid added a commit that referenced this issue Sep 4, 2024
erkannt added a commit that referenced this issue Sep 4, 2024
thewilkybarkid added a commit that referenced this issue Sep 4, 2024
We've decided to put all the context tags in one module, which different parts of the application can depend on. This keeps the tags separate from the implementations.

Refs #1834
thewilkybarkid added a commit that referenced this issue Sep 11, 2024
thewilkybarkid added a commit that referenced this issue Sep 11, 2024
thewilkybarkid added a commit that referenced this issue Sep 12, 2024
thewilkybarkid added a commit that referenced this issue Sep 12, 2024
I've not seen it happen, but it's safer to set the event listener before starting processing.

Refs #1834
thewilkybarkid added a commit that referenced this issue Sep 19, 2024
thewilkybarkid added a commit that referenced this issue Sep 19, 2024
thewilkybarkid added a commit that referenced this issue Sep 19, 2024
thewilkybarkid added a commit that referenced this issue Sep 20, 2024
thewilkybarkid added a commit that referenced this issue Sep 20, 2024
thewilkybarkid added a commit that referenced this issue Sep 20, 2024
thewilkybarkid added a commit that referenced this issue Sep 20, 2024
thewilkybarkid added a commit that referenced this issue Sep 20, 2024
thewilkybarkid added a commit that referenced this issue Sep 25, 2024
If the client drops the connection, Effect recognises this and finishes the response with '204 No Content'. Routes that are still served by hyper-ts, however, then try to send a response that Node rejects. This change recognises these and skips over them to avoid noisy log messages.

Refs #1834, https://expressjs.com/en/guide/error-handling.html, https://discord.com/channels/795981131316985866/1283492544256278601/1283741118168829973
thewilkybarkid added a commit that referenced this issue Sep 25, 2024
thewilkybarkid added a commit that referenced this issue Sep 26, 2024
thewilkybarkid added a commit that referenced this issue Oct 2, 2024
As the Effect server catches defects and returns a 500 response, we need to see when this happens.

Refs #1834, #1973
thewilkybarkid added a commit that referenced this issue Oct 7, 2024
`express.use()` is stateful, so a middleware was added on each request handled. This change creates a fresh Express app on each request instead, which feels wasteful but should remove the leak.

Refs #1834, e33d15d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant