| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Performance Report✔️ no performance regression detected Full benchmark results
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Motivation
Noticed that after changes done in #5795 the error listener will always be called after socket close listener. This means that calling reject will not do anything as promise is already resolved.
As per my understanding, it was redundant before as well because the only error it would report is ECONNRESET if client disconnects which we don't want to log on the server (see previous PR #5722).
These two PRs on node further indicate that the only error event that is emitted is due to client disconnect (ECONNRESET)
If there are actual error trying to write an event to the stream on the server, it would be caught by this
lodestar/packages/api/src/beacon/server/events.ts
Lines 42 to 44 in 7f19831
The server is not really concerned about anything else than writing data, if there is an error it must be detected by the client which is what we are doing already.
Invalid json data sent would be detected here
lodestar/packages/api/src/beacon/client/events.ts
Lines 25 to 28 in ec0a60f
and any other errors are caught here and reported here
lodestar/packages/api/src/beacon/client/events.ts
Lines 34 to 42 in ec0a60f
Description
Remove redundant eventstream error listener on the server.