Closed alexwei closed 6 years ago
That's true. We'll have a fix for this soon.
Related: the stacktraces for exceptions like this are not particularly useful - we should be logging them only at debug level.
This has been fixed in version 4.2.2. Thanks for pointing it out.
The issue is still present in the code, the flag key is not being logged: https://github.com/launchdarkly/java-server-sdk/blob/13d01ff4536de42d0445cd3ab93859fa84c861d3/src/main/java/com/launchdarkly/sdk/server/LDClient.java#L509
Our codebase has async requests coming in to evaluate feature flag, and we have seen some flags assuming different result type when what is set on LD, but it's very hard for us to find out the culprit flag.
It would be helpful if the error message actually includes the key of the flag.