We don't how know the user application is written, there can be some cases where some connections do not get closed after the termination of the application.
In such cases, keploy proxy can also get errors eg: EOF, connection reset by peer, etc. We should not log these errors.
Right now, only EOF is handled if the app is closed gracefully, for other cases, keploy proxy should be aware of the application status.
Steps to reproduce
Record some test cases and mocks for your application.
During test mode, abruptly close the application by sending SIGKILL or SIGTERM to the app PGID.
Is there an existing issue for this?
Current behavior
Steps to reproduce
Environment
None
Version
Local
Repository
keploy