Skip to content

Pipeline tests part 2 #14951

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

Merged
merged 65 commits into from
Jun 30, 2025
Merged

Pipeline tests part 2 #14951

merged 65 commits into from
Jun 30, 2025

Conversation

cherylEnkidu
Copy link
Contributor

No description provided.

Copy link
Contributor

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

@google-oss-bot
Copy link

1 Warning
⚠️ Did you forget to add a changelog entry? (Add #no-changelog to the PR description to silence this warning.)

Generated by 🚫 Danger

@cherylEnkidu cherylEnkidu force-pushed the cheryllin/ppltests2 branch from 47785df to 51086da Compare June 11, 2025 17:52
Base automatically changed from cheryllin/ppltests1 to cheryllin/ppl June 17, 2025 18:28
result.map_value.fields[0].key = nanopb::MakeBytesArray("expression");
result.map_value.fields[0].value = expr_->to_proto();
result.map_value.fields[1].key = nanopb::MakeBytesArray("direction");

Copy link
Contributor

Choose a reason for hiding this comment

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

Curious why the "order" is flipped here. It is a map, so the order should not matter?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It should not matter. I changed this when I debugging other things and doing a cross comparison with the web sdk.

@wu-hui wu-hui assigned cherylEnkidu and unassigned wu-hui Jun 30, 2025
@cherylEnkidu cherylEnkidu merged commit 432064a into cheryllin/ppl Jun 30, 2025
28 of 32 checks passed
@cherylEnkidu cherylEnkidu deleted the cheryllin/ppltests2 branch June 30, 2025 17:51
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.

4 participants