Skip to content

Update non prod feature flag to 0.6 threshold - #6571

Open
shixiao-coder wants to merge 2 commits into
datacommonsorg:masterfrom
shixiao-coder:update-non-prod-feature-flag-to-0.6-threshold
Open

Update non prod feature flag to 0.6 threshold#6571
shixiao-coder wants to merge 2 commits into
datacommonsorg:masterfrom
shixiao-coder:update-non-prod-feature-flag-to-0.6-threshold

Conversation

@shixiao-coder

Copy link
Copy Markdown
Contributor

This PR update the feature flag for autopush, staging, custom, dev and local environment to set detect-and-fulfill threshold to 0.6 from 0.7

It also include the goldens rebases that was done and reverted from #6533

{
"tiles": [
{
"type": "PLACE_OVERVIEW"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

verified the change is reasonable, it will filter out all SV with threshold 0.7 and able to capture SV with threshold 0.6

@gemini-code-assist

Copy link
Copy Markdown
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 updates feature flag configurations for non-production environments to enable the spanner embedding threshold. It also includes comprehensive updates to various integration test golden files to ensure they remain consistent with the current state of the application.

Highlights

  • Feature Flag Configuration: Enabled the 'use_config_threshold_for_spanner_embedding' feature flag across autopush, custom, dev, local, and staging environments.
  • Integration Test Updates: Performed extensive rebasing and updates to integration test golden files to align with recent system changes.
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 the 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 counterproductive. 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.

@@ -10,308 +10,115 @@
"tiles": [

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

restores back to two SVs as the test intended

@@ -10,55 +10,28 @@
"tiles": [

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

properly filter-in MultiSV after threshold decrease

@@ -9,29 +9,21 @@
{
"tiles": [

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

heuristic dection type can already find SVs above threshold and didn't goes to LLM detection like before

@@ -131,6 +131,38 @@
"denom": "Count_Person",

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

we have more SVs to show with lower threshold and not showing the related like before

@@ -9,20 +9,23 @@
{
"tiles": [

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

we are able to capture the 2 SV like the NL server

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

Copy link
Copy Markdown
Contributor

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 several configuration files to include new data visualizations, such as unemployment rates, criminal activity statistics, and housing metrics. The changes involve adding new chart blocks and updating statistical variable specifications across multiple test data files. My review identified that some chart titles are repetitive, which could hinder user experience, and noted a discrepancy in the user message for a specific query regarding California counties.

}
],
"denom": "Count_Person",
"title": "Crimes by Type in Cities of San Francisco Bay Area"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The title "Crimes by Type in Cities of San Francisco Bay Area" is repeated for multiple chart blocks (for Aggravated Assault, Arson, Burglary, etc.). This will create several sections with the exact same title in the UI, which can be confusing for users.

To improve clarity, each block should have a more specific title that reflects its content. For example, this block could be titled "Aggravated Assault" and the next one "Arson", and so on.

"svSource": "CURRENT_QUERY",
"svSource": "UNKNOWN",
"test": "filter_test",
"userMessages": []

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The user message "Sorry, there were no relevant statistics for cities in California. See results for United States." seems incorrect for this query. The original query was about "counties in California", not cities. Furthermore, the results shown are for California counties, not for the United States. The message is misleading to the user.

@@ -73,10 +73,335 @@
{

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The lower threshold causing the valid char vars (Topic + SVs) goes from 2 to >40, and changes the max number of chart shown for given var from 10 to 3 and cause the chart difference

@@ -103,10 +103,40 @@
{
"tiles": [

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

this is just a change in place for query_2 and follows the same comment above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant