Show stoper bug do to parseInt #4
Merged
Conversation
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
Algunenano
pushed a commit
to Algunenano/node-postgres
that referenced
this pull request
May 8, 2018
Fix node-postgres vulnerability for branch: cdb-2.6
brianc
added a commit
that referenced
this pull request
Dec 20, 2019
maxListeners on timestamp queries
brianc
pushed a commit
that referenced
this pull request
Dec 27, 2019
This pull request was closed.
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.
I added a test and fixed the bug.
I am not to comfortable with node and testing in javascript so you might want to change the test.
You can read about whats wrong with parseInt here.
http://www.breakingpar.com/bkp/home.nsf/0/87256B280015193F87256C85006A6604