-
**Describe the bug**
We are getting 800 users getting a crash - its a small amount of users but enough for investigation.
**To reproduce**
Unable to reproduce.
**Expected behavior**
Not to cr…
-
We have a Redis datastore that we've been testing with successfully with a password until we introduced the username. I can confirm that the connection works with the username/password when using the…
-
**Describe the bug**
`waitForInitialization` is returning an internal `LDClient` type, instead of the `LDClient` that is exported, causing TypeScript compile errors if I want to use the output from…
-
**Describe the bug**
Beginning around May 7, 2024, the Erlang Server SDK stopped connecting to the streaming FedRAMP server at https://stream.launchdarkly.us. This seems to be due to a cipher mismat…
-
Hey LD Team,
I am facing a crash on launch after upgrading to v5.3.0.
**Logs**
```
Caused by:
java.lang.NullPointerException: Attempt to invoke interface method 'java.lang.Object
java.util…
-
**Is your feature request related to a problem? Please describe.**
In order to get the Launch Darkly dashboard to correctly report when flags are evaluated ("Evaluated xxx mins ago" on the flag pag…
-
**Describe the bug**
When creating an LdClient with a Server SDK key, it never seems to initialise despite receiving a 200 status code.
Attempting to troubleshoot network issues, I tried connectin…
-
**Description**
The FlagValueChanged event does not fire on the first event after initializing if `AutoEnvAttributes` is enabled.
**To reproduce**
Use the following code to initialize `LdClient` …
-
```
> rails c
[1] pry(main)> [LDClient] sending 2 events: [{"kind":"index","...}]}}}]
```
You have to hit enter to skip past it
-
Looking for guidance and/or best-practices for trying to understand how best to make sure the persistent connection to Launchdarkly closes cleanly, as we're having an issue with our process being held…