You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've discovered an embarrassing bug in the latest release, 5.5.3. The symptom is that when the SDK client starts up, it may immediately throw a NameError ("uninitialized constant LaunchDarkly::Util::Net"). Whether this happens or not depends on what other gems have been loaded (we were missing a require "net/http", but many other gems can provide that dependency, thereby masking the error).
The error is only present in version 5.5.3. This will be fixed in a patch release very soon.
The text was updated successfully, but these errors were encountered:
We've discovered an embarrassing bug in the latest release, 5.5.3. The symptom is that when the SDK client starts up, it may immediately throw a
NameError
("uninitialized constant LaunchDarkly::Util::Net"). Whether this happens or not depends on what other gems have been loaded (we were missing arequire "net/http"
, but many other gems can provide that dependency, thereby masking the error).The error is only present in version 5.5.3. This will be fixed in a patch release very soon.
The text was updated successfully, but these errors were encountered: