[GODRIVER-2874] Initial connection handshake does not publish heartbeat Created: 18/Jun/23  Updated: 28/Oct/23  Resolved: 20/Jun/23

Status: Closed
Project: Go Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 1.12.0

Type: Bug Priority: Unknown
Reporter: Preston Vasquez Assignee: Preston Vasquez
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by GODRIVER-2577 Heartbeat build up with streaming pro... Closed
Related
is related to GODRIVER-2123 Use an administrative Client in test ... Backlog
Backwards Compatibility: Fully Compatible
Documentation Changes: Not Needed
Documentation Changes Summary:

1. What would you like to communicate to the user about this feature?
2. Would you like the user to see examples of the syntax and/or executable code and its output?
3. Which versions of the driver/connector does this apply to?


 Description   

When a connection is made, the following order is expected:

  • Create Monitor
  • run handshake ("ismaster" with client metadata, without maxAwaitTimeMS)
  • get handshake response
  • publish HeartbeatSucceededEvent

GODRIVER-2577 introduced a bug that prevents the block that is responsible for publishing a heartbeat succeeded event, using the “isNilConn” variable which is not reset from the original declaration.
 



 Comments   
Comment by Githook User [ 20/Jun/23 ]

Author:

{'name': 'Preston Vasquez', 'email': 'prestonvasquez@icloud.com', 'username': 'prestonvasquez'}

Message: GODRIVER-2874 Directly reference conn existence (#1300)
Branch: master
https://github.com/mongodb/mongo-go-driver/commit/30f817c1df6a0f7c41f189418b06381a29ff4701

Generated at Thu Feb 08 08:39:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.