Suppress error events.

[jameshilliard]

Fixes:

node:events:353
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at TCP.onStreamRead (node:internal/stream_base_commons:213:20)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:188:8)
    at emitErrorCloseNT (node:internal/streams/destroy:153:3)
    at processTicksAndRejections (node:internal/process/task_queues:80:21) {
  errno: -54,
  code: 'ECONNRESET',
  syscall: 'read'
}
npm ERR! code 1

[Copilot]

Pull Request Overview

This PR addresses unhandled error events that were causing the application to crash with ECONNRESET errors by adding an empty error handler to the response object.

• Adds an error event listener to suppress connection reset errors
• Prevents application crashes from unhandled socket errors

[Copilot]

Silently suppressing all errors with an empty handler is risky and makes debugging difficult. Consider logging the error or handling specific error types appropriately.

Suggested change

	res.on('error', () => {});
	res.on('error', (err) => {
	console.error('Error in fake_response res:', err);
	});

[Copilot]

The empty error handler provides no context about what errors are being suppressed. At minimum, consider adding a comment explaining why errors are being ignored or log them for debugging purposes.

Suggested change

	res.on('error', () => {});
	res.on('error', (err) => {
	// Log the error for debugging purposes
	console.error('Error in fake_response:', err);
	});