Unix Socket Cleanup Issue in Effect Implementation
Total sanity check related to ^ and I assume I'm wrong but:
I have a non-Effect implementation of a Node server that listens on a Unix socket, and process restarts in development work fine. When a new application starts, it unlinks the socket and reconnects to it, before the old process quits (this is an Electron development thing I can't easily avoid). However, in the Effect implementation, it seems like something is cleaning up the socket on exit, which is not what I want. It ends up creating a race condition where the process restarts before the old one exits, and the old one rms the socket that the new one has connected to.
I have a non-Effect implementation of a Node server that listens on a Unix socket, and process restarts in development work fine. When a new application starts, it unlinks the socket and reconnects to it, before the old process quits (this is an Electron development thing I can't easily avoid). However, in the Effect implementation, it seems like something is cleaning up the socket on exit, which is not what I want. It ends up creating a race condition where the process restarts before the old one exits, and the old one rms the socket that the new one has connected to.
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
