We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
It looks like the fix Allow string and uint values in Event.IncidentType by isimluk · Pull Request #206 · CrowdStrike/gofalcon didn't completely resolve the issue stream error "json: cannot unmarshal string into Go struct field Event.event.IncidentType of type uint64" · Issue #205 · CrowdStrike/gofalcon. The Event.event.IncidentType could be some string literals that can not be unmarshalled into json.Number type. Your help to address this issue is much appreciated.
Kevin
The text was updated successfully, but these errors were encountered:
Streaming API: Accept string values, when uint64 is expected
203e1f2
Fixes: CrowdStrike#215 Addressing: stream error "json: invalid number literal, trying to unmarshal "\"DOMAIN_COMPROMISE\"" into Number"
Successfully merging a pull request may close this issue.
Hi,
It looks like the fix Allow string and uint values in Event.IncidentType by isimluk · Pull Request #206 · CrowdStrike/gofalcon didn't completely resolve the issue stream error "json: cannot unmarshal string into Go struct field Event.event.IncidentType of type uint64" · Issue #205 · CrowdStrike/gofalcon. The Event.event.IncidentType could be some string literals that can not be unmarshalled into json.Number type. Your help to address this issue is much appreciated.
Kevin
The text was updated successfully, but these errors were encountered: