chore: enable e2e-bm in ci.

[k82cn]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @k82cn, 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 refactors the continuous integration (CI) configuration by renaming an existing file and introducing a new YAML configuration for a local 'flame' cluster. These changes are part of an effort to enable end-to-end benchmarks within the CI pipeline, providing a dedicated and detailed setup for the 'flame' environment's network services and package management.

Highlights

• CI Configuration File Renaming: The configuration file ci/flame-local-conf.yaml has been renamed to ci/flame-cluster-local.yaml to provide a more descriptive name reflecting its purpose.
• New Local Flame Cluster Configuration: A new configuration file, ci/flame-local.yaml, has been added. This file defines the setup for a local 'flame' cluster, including its HTTP endpoint, gRPC cache endpoint, package storage path, and exclusion patterns for package files.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/e2e-bm.yaml

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

[gemini-code-assist]

Code Review

This pull request renames a configuration file and introduces a new client-side configuration for a local Flame cluster (ci/flame-local.yaml). This change is crucial for enabling e2e-bm in CI. However, there are critical mismatches in the endpoint and cache endpoint configurations in the newly added file, which will prevent successful connection to the local cluster services.

[gemini-code-assist]

The endpoint port 8080 in this client configuration file (ci/flame-local.yaml) does not match the endpoint port 30080 configured for the local Flame session manager in ci/flame-cluster-local.yaml. This mismatch will prevent the client from connecting to the session manager.

    endpoint: "http://127.0.0.1:30080"

[gemini-code-assist]

The cache.endpoint protocol grpc in this client configuration file (ci/flame-local.yaml) does not match the http protocol configured for the local cache endpoint in ci/flame-cluster-local.yaml. This protocol mismatch will prevent the client from connecting to the cache service.

      endpoint: "http://127.0.0.1:9090"