[4.3]Fixed dialyzer issues that came up from running dialyze hard after 4.3.136 merge #6692
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bradfordben
force-pushed
the
upstream-4.3-dialyzer_fixes
branch
3 times, most recently
from
3a084e4
to
ae70677
Compare
jamesaimonetti
pushed a commit
that referenced
this pull request
Feb 1, 2021
|
merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dialyze hard identified some issues in kazoo proper and kz_http. Pulled in dialyzer fixes for kz_http and fixed csv proper bug