-
Notifications
You must be signed in to change notification settings - Fork 26
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.
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
Fix case clause error #29
Conversation
%{status_code: status, data: body} | ||
|> normalize_response | ||
|
||
%HTTPotion.ErrorResponse{} = error -> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the primary change
status_code: integer, | ||
status_txt: binary, | ||
} | ||
data: binary, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rest of this stuff is formatter changes
|
||
otp_release: | ||
- "19.3" | ||
- "20.2" | ||
- "20.3" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or changing dependencies to get things to build
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MaxPower15 I assume you're the one with power to publish? |
NSQ can be flaky over the network. If the request times out, it causes a case clause match error causing the process to crash. If the network remains flaky, the failure can cascade up the supervision tree, causing the whole application to crash.