Handling network errors in ClientServerInputMultiplexer
See original GitHub issueWe get these network failures logged as errors and they are not “errors” in some cases… If the other side stops, which the client still tries to communicate with it, you will get such errors. It would be great if there would be some callback support here and there, where clients can decide what is worth logging as an error.
2020-05-04 09:49:39,725 [RSocket-epoll-2] ERROR io.rsocket.FrameLogger - Error receiving frame:
io.netty.channel.unix.Errors$NativeIoException: readAddress(..) failed: Connection reset by peer
Issue Analytics
- State:
- Created 3 years ago
- Comments:30 (14 by maintainers)
Top Results From Across the Web
Handling network errors in grpc-java - Stack Overflow
How can I implement a strategy to detect and try to recover from network errors using gRPC-java? I know that UNAVAILABLE status can...
Read more >Error Handling - Apollo GraphQL Docs
A network error results in a .failure(Error) result for the operation. You can handle network errors by using a do/catch block and calling...
Read more >How to track network errors | THEOplayer Documentation
How to track network errors. THEOplayer currently doesn't throw an error event for all network request errors on all platforms. Sometimes you might...
Read more >5.5. Network error handling — Anjay 3.1.2 documentation
... over the network, Anjay needs to be prepared to handle communication errors. This page documents the library's behavior during various error conditions....
Read more >Dealing with network errors | Rest Hooks
Dealing with network errors. When you use the useSuspense() hook, React will suspend rendering while the network request takes place.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@rstoyanchev Perfectly agree with the purpose of logging what’s on the wire for RSocket … however, if there is an error, one could expect to be notified on the doOnError? It should not be the role of the “logger” class … I would think?
closing this one since it looks resolved