Protecting long numbers while JSON Unmarshal#2
Open
dharmarth wants to merge 3 commits intojpoehls:masterfrom
Open
Protecting long numbers while JSON Unmarshal#2dharmarth wants to merge 3 commits intojpoehls:masterfrom
dharmarth wants to merge 3 commits intojpoehls:masterfrom
Conversation
…andling generic Conduit response.result.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Ran into connection issue after upgrading Phabricator. Looks updated version of Phabricator is giving long number for ConnectionID. When doing JSON unmarshal, it gets converted into floating point number http://stackoverflow.com/questions/22343083/json-marshaling-with-long-numbers-in-golang-gives-floating-point-number
Patch to prevent it from happening.