Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Streaming API: Accept string values, when uint64 is expected #216

Merged
merged 1 commit into from
Apr 8, 2022
Merged

Streaming API: Accept string values, when uint64 is expected #216

merged 1 commit into from
Apr 8, 2022

Conversation

isimluk
Copy link
Contributor

@isimluk isimluk commented Apr 8, 2022

Fixes: #215

Addressing:

stream error "json: invalid number literal, trying to unmarshal "\"DOMAIN_COMPROMISE\"" into Number"

@isimluk
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"
@redhatrises redhatrises merged commit e9add72 into CrowdStrike:main Apr 8, 2022
@isimluk isimluk deleted the fix-215 branch April 8, 2022 14:06
@kliao365 kliao365 mentioned this pull request Apr 18, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

stream error "json: invalid number literal, trying to unmarshal "\"DOMAIN_COMPROMISE\"" into Number"
2 participants
@isimluk @redhatrises