Open ericatdropzone opened 1 year ago
Well this is disappointing. We've had to work around Splunk returning incorrectly encoded XML is the case of binary data, and I was hoping that in the switch to JSON they would have fixed that. So now we can look ahead to working around this in JSON as well (yay!)
I'm using the botsv3 dataset and running running code similar to this:
I'm seeing this exception:
This looks similar to this issue, but running version 1.7.4 didn't fix this instance of the problem. I also noticed that this pull request appears to fix the issue, but I'm not sure if that's the approach you'd want to take
Splunk (please complete the following information):
SDK (please complete the following information):