Constructing a client via ClientOptions does not validate heartbeatFrequencyMS

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Unknown
    • 2.4.0
    • Affects Version/s: 2.3.0
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When constructing a client via ClientOptions (and not via a URI), no validation is performed on heartbeatFrequencyMS. This allows the user to specify a heartbeatFrequencyMS that is lower than minHeartbeatFrequencyMS, which results in a subtract overflow and panic of a monitoring task. We should validate this option regardless of how the user constructs the client.

              Assignee:
              Patrick Freed
              Reporter:
              Patrick Freed
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: