-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem: subscription refactoring not merged #375
Conversation
* Problem: internal websocket connection is heavy and unstable Solution: - use local node client directly. * ignore duplicate subscriptions, it's possible in concurrency * bigger start timeout * handle error * fix lint * fix unit test * rename * fix test * remove test * add buffer
* implement stream * rpc stream * websocket use stream * filter apis use stream * cleanup * move modules * cleanup * fix cond race * fix lint * nit * fix build * fix lint * err return * fix empty logs * fix filter initial offset * fix filter * fix filter * fix test
}, api.logger, "closing websocket peer sub") | ||
try(func() { | ||
if err != websocket.ErrCloseSent { | ||
_ = wsConn.Close() |
Check warning
Code scanning / gosec
Returned error is not propagated up the stack. Warning
if err != nil { | ||
try(func() { | ||
if err != websocket.ErrCloseSent { | ||
_ = wsConn.Close() |
Check warning
Code scanning / gosec
Returned error is not propagated up the stack. Warning
api.logger.Debug("dropping NewHeads WebSocket subscription", "subscription-id", subID, "error", err.Error()) | ||
try(func() { | ||
if err != websocket.ErrCloseSent { | ||
_ = wsConn.Close() |
Check warning
Code scanning / gosec
Returned error is not propagated up the stack. Warning
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need an improvement change log?
sure, added. |
* Problem: internal websocket connection is heavy and unstable (#373) * Problem: internal websocket connection is heavy and unstable Solution: - use local node client directly. * ignore duplicate subscriptions, it's possible in concurrency * bigger start timeout * handle error * fix lint * fix unit test * rename * fix test * remove test * add buffer * Problem: channels are not efficient for broadcasting scenario (#374) * implement stream * rpc stream * websocket use stream * filter apis use stream * cleanup * move modules * cleanup * fix cond race * fix lint * nit * fix build * fix lint * err return * fix empty logs * fix filter initial offset * fix filter * fix filter * fix test * changelog * add comments
Description
Merge the feature into develop branch.
For contributor use:
docs/
) or specification (x/<module>/spec/
)godoc
comments.Unreleased
section inCHANGELOG.md
Files changed
in the Github PR explorerFor admin use:
WIP
,R4R
,docs
, etc)