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.
Leonlu2/error on geo values #1095
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
Leonlu2/error on geo values #1095
Changes from 8 commits
dd8c5c8
d024995
a6cc058
6ed27d9
e89692e
14463c8
3648a74
e884b7c
9fe6196
6dac204
7b7b5e7
0a2bdf9
ef362d8
6e29946
e3fe68b
43a232e
e3054cd
1e75209
5fed93c
79cdc26
bec5621
4578420
4a59ead
00b4ff2
58fcc7f
94e8b5f
59ce3c9
d41eeaa
b01bb82
e2d12ee
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
is it your intention to make rows with invalid
geo_value
s here? maybe you want to use some fromFIPS
instead?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.
why dont we see the "invalid geo" messages when we use this row set?
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.
Oh sorry that I overlooked these comments, somehow it did not show on the conversation page. Yeah I think using some FIPS here would be good.
I think we don't see "invalid geo" because the make_default_row(base function here) does not go through the geo validator in the server maybe?
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.
make_default_row()
doesnt check them, youre right. it looks like whenever sample rows from_insert_placeholder_set_three
are used, certain subsets of them are isolated and sometimes thegeo_value
s are changed before theyre passed torequest_based_on_row()
where they are actually checked for geo validation, and badgeo_value
s were never sent in a request.