-
Notifications
You must be signed in to change notification settings - Fork 88
fix: Add atomic.Bool to ensure wsConnection.Disconnect() is only called once #359
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
Open
shazlehu
wants to merge
3
commits into
open-telemetry:main
Choose a base branch
from
observIQ:fix/extra-error-log
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -4,6 +4,7 @@ import ( | |||||
"context" | ||||||
"net" | ||||||
"sync" | ||||||
"sync/atomic" | ||||||
|
||||||
"github.com/gorilla/websocket" | ||||||
|
||||||
|
@@ -17,23 +18,31 @@ type wsConnection struct { | |||||
// The websocket library does not allow multiple concurrent write operations, | ||||||
// so ensure that we only have a single operation in progress at a time. | ||||||
// For more: https://pkg.go.dev/github.com/gorilla/websocket#hdr-Concurrency | ||||||
connMutex *sync.Mutex | ||||||
connMutex sync.Mutex | ||||||
wsConn *websocket.Conn | ||||||
closed atomic.Bool | ||||||
} | ||||||
|
||||||
var _ types.Connection = (*wsConnection)(nil) | ||||||
|
||||||
func (c wsConnection) Connection() net.Conn { | ||||||
func newWSConnection(wsConn *websocket.Conn) types.Connection { | ||||||
return &wsConnection{wsConn: wsConn, connMutex: sync.Mutex{}, closed: atomic.Bool{}} | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think zero-initialization for connMutex and closed is fine, e.g. this should work the same way and is less verbose:
Suggested change
|
||||||
} | ||||||
|
||||||
func (c *wsConnection) Connection() net.Conn { | ||||||
return c.wsConn.UnderlyingConn() | ||||||
} | ||||||
|
||||||
func (c wsConnection) Send(_ context.Context, message *protobufs.ServerToAgent) error { | ||||||
func (c *wsConnection) Send(_ context.Context, message *protobufs.ServerToAgent) error { | ||||||
c.connMutex.Lock() | ||||||
defer c.connMutex.Unlock() | ||||||
|
||||||
return internal.WriteWSMessage(c.wsConn, message) | ||||||
} | ||||||
|
||||||
func (c wsConnection) Disconnect() error { | ||||||
func (c *wsConnection) Disconnect() error { | ||||||
if !c.closed.CompareAndSwap(false, true) { | ||||||
return nil | ||||||
} | ||||||
return c.wsConn.Close() | ||||||
} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 care about the log messages produced? It looks fragile to make the tests dependent on the exact formatting of the messages.
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.
Agree we should avoid fragility. The original motivation for this change was to deal with superfluous error logs produced by the server-side Disconnect() calls. Open to suggestions for a better criteria for to test for.
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.
Perhaps as a compromise: in testLogger store error logs separate from debug logs and here only assert that there is an error log produced, but don't check the error message itself. This should be fairly stable since we always expect exactly one error log and don't really care about the message itself.