Fix Playground Frontend Test job

[Amar3tto]

Fixes #37478
Flutter tests are successful

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[gemini-code-assist]

Summary of Changes

Hello @Amar3tto, I'm Gemini Code Assist¹! 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 addresses a failing frontend test job by precisely defining the versions of several Flutter package dependencies. By pinning these dependencies to known working versions or ranges, it ensures compatibility and stability for the Playground Frontend, resolving the issues that were causing tests to fail.

Highlights

• Dependency Version Pinning: The app_state dependency has been pinned to version 0.9.4 across multiple pubspec.yaml files.
• Dependency Version Range Update: The easy_localization dependency has been updated to a specific version range >=3.0.1 <3.0.3 in playground/frontend/playground_components/pubspec.yaml and playground/frontend/pubspec.yaml.
• Dependency Version Pinning: The keyed_collection_widgets dependency has been pinned to version 0.4.3 in playground/frontend/playground_components/pubspec.yaml and playground/frontend/playground_components_dev/pubspec.yaml.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• playground/frontend/playground_components/pubspec.yaml
  • Updated app_state dependency to 0.9.4.
  • Updated easy_localization dependency to >=3.0.1 <3.0.3.
  • Updated keyed_collection_widgets dependency to 0.4.3.
• playground/frontend/playground_components_dev/pubspec.yaml
  • Updated app_state dependency to 0.9.4.
  • Updated keyed_collection_widgets dependency to 0.4.3.
• playground/frontend/pubspec.yaml
  • Updated app_state dependency to 0.9.4.
  • Updated easy_localization dependency to >=3.0.1 <3.0.3.

Activity

• The author has confirmed that Flutter tests are now successful after these changes.
• A link to a successful GitHub Actions run has been provided, demonstrating the fix.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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. ↩

[github-actions]

Assigning reviewers:

R: @damccorm for label build.

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[damccorm]

I have a couple of questions:

1. Do we need to comment this out entirely or could we target a specific test (or at least

   beam/playground/frontend/build.gradle

   Line 190 in 120ceab

   dependsOn("integrationTest_standalone_default_examples")

   )?
2. Could you please file an issue to track this issue/reenabling these tests and link from here?
3. Do we understand why these tests are failing?