Skip to content

Automated Integration Test Goldens Update from CI#6095

Merged
SandeepTuniki merged 1 commit intomigrate-place-info-v2-golden-updatesfrom
nl-golden-update-276e2d55-2442-41f1-80c0-2922463dcc7d
Mar 18, 2026
Merged

Automated Integration Test Goldens Update from CI#6095
SandeepTuniki merged 1 commit intomigrate-place-info-v2-golden-updatesfrom
nl-golden-update-276e2d55-2442-41f1-80c0-2922463dcc7d

Conversation

@datacommons-robot-author
Copy link
Collaborator

@datacommons-robot-author datacommons-robot-author commented Mar 18, 2026

This pull request updates the golden files automatically via Cloud Build. Please review the changes carefully. Cloud Build Log

Edit from @SandeepTuniki: Don't review/approve. I triggered this PR creation manually (through cloudbuild) as part of my work in #6047. I'll club the changes of this PR into #6047.

@datacommons-robot-author datacommons-robot-author requested review from a team and clincoln8 and removed request for a team March 18, 2026 04:47
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on updating various golden files used in integration tests. These updates are automatically generated by the CI pipeline, reflecting necessary adjustments to expected outputs due to underlying data changes, improved place type definitions, or minor precision refinements in debug information. The changes ensure the test suite remains accurate and aligned with current system behavior.

Highlights

  • Automated Golden File Updates: This pull request contains automated updates to golden files, ensuring integration tests reflect the latest expected outputs from the system's logic or data.
  • Place Type Normalization: The place_type for 'San Francisco' was updated from 'City' to 'AdministrativeArea2' in a chart configuration, standardizing place classifications.
  • Precision Adjustments in Debug Info: Minor floating-point precision adjustments were made in two debug_info.json files, likely reflecting subtle changes in calculation or data representation.
  • Geographical Naming Consistency: Multiple chart titles and descriptions related to 'New York' were updated to 'New York City' for improved clarity and consistency.
  • Enhanced Mexico City Place Detection Data: Significant updates were made to the Mexico City place detection golden file, including the addition of new ranking tiles, more granular place type definitions, and a comprehensive list of child administrative areas.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@SandeepTuniki SandeepTuniki removed the request for review from clincoln8 March 18, 2026 04:48
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates golden test files. Most changes are minor and expected, such as updates to place names, types, and floating point precision. However, I've found a couple of potential issues in the updated chart_config.json for Mexico City. The new data includes duplicate entries for 'Tlalpan' as a child place, and the list of peer places for Mexico City is now empty, which might be a regression. Please see the specific comments for details.

Comment on lines +410 to +523
"AdministrativeArea2": [
{
"dcid": "wikidataId/Q10832464",
"name": "Venustiano Carranza",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q14906254",
"name": "\u00c1lvaro Obreg\u00f3n",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q1832732",
"name": "Miguel Hidalgo",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q2027082",
"name": "Gustavo A. Madero",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q2356998",
"name": "Benito Ju\u00e1rez de Ochoa Quiroz",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q408181",
"name": "Tl\u00e1huac",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q408187",
"name": "Tlalpan",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q643026",
"name": "Xochimilco",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q645293",
"name": "Cuauht\u00e9moc",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q661315",
"name": "Coyoac\u00e1n",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q741771",
"name": "Iztapalapa",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q762749",
"name": "Cuajimalpa",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q780038",
"name": "La Magdalena Contreras",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q936087",
"name": "Milpa Alta",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q953866",
"name": "Tlalpan",
"types": [
"AdministrativeArea2"
]
},
{
"dcid": "wikidataId/Q994867",
"name": "Azcapotzalco",
"types": [
"AdministrativeArea2"
]
}
]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The childPlaces list for AdministrativeArea2 contains two different entries for "Tlalpan" with different dcids (wikidataId/Q408187 and wikidataId/Q953866). This duplication might indicate an underlying data quality issue and could lead to confusion or incorrect behavior in the UI. It would be best to investigate and ensure only the correct entity for Tlalpan is included.

]
}
],
"peerPlaces": [],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The peerPlaces list is now empty, whereas it previously contained a list of major world cities. This could be a regression. Was it intended for Mexico City to no longer have any peer places after its type changed from City to AdministrativeArea1? This might affect comparison features.

@SandeepTuniki SandeepTuniki merged commit 1029f44 into migrate-place-info-v2-golden-updates Mar 18, 2026
1 of 2 checks passed
@SandeepTuniki SandeepTuniki deleted the nl-golden-update-276e2d55-2442-41f1-80c0-2922463dcc7d branch March 18, 2026 04:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants