-
Notifications
You must be signed in to change notification settings - Fork 811
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
gemini 1.5 pro & flash #1308
gemini 1.5 pro & flash #1308
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Looks good to me! Reviewed everything up to 978b0cd in 36 seconds
More details
- Looked at
23
lines of code in1
files - Skipped
0
files when reviewing. - Skipped posting
1
drafted comments based on config settings.
1. skyvern/forge/sdk/api/llm/config_registry.py:263
- Draft comment:
The configuration key "GEMINI_FLUSH" might be a typo. Consider renaming it to "GEMINI_FLASH" for consistency with the naming convention. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable:
The comment is addressing a potential inconsistency between the configuration key 'GEMINI_FLUSH' and the model name 'gemini/gemini-1.5-flash'. This could be a valid point if the naming convention is to match the key with the model name. However, without additional context on naming conventions, it's speculative. The comment is about a change made in the diff, so it is relevant.
I might be overestimating the importance of matching the configuration key with the model name. The naming might be intentional for reasons not visible in the diff.
Without clear evidence that the naming is intentional, it's reasonable to consider the comment as potentially valid. However, the lack of strong evidence means the comment might be speculative.
The comment is speculative and lacks strong evidence of an issue. It should be deleted as it does not meet the criteria for a necessary code change.
Workflow ID: wflow_SOF0Meli6WzHQCtK
You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet
mode, and more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❌ Changes requested. Incremental review on 0aee3c2 in 41 seconds
More details
- Looked at
14
lines of code in1
files - Skipped
0
files when reviewing. - Skipped posting
0
drafted comments based on config settings.
Workflow ID: wflow_UATD8vOAnHjwACgO
Want Ellipsis to fix these issues? Tag @ellipsis-dev
in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet
mode, and more.
@@ -285,7 +285,8 @@ More extensive documentation can be found on our [documentation website](https:/ | |||
| `ENABLE_AZURE` | Register Azure OpenAI models | Boolean | `true`, `false` | | |||
| `ENABLE_BEDROCK` | Register AWS Bedrock models| Boolean | `true`, `false` | | |||
| `ENABLE_GEMINI` | Register Gemini models| Boolean | `true`, `false` | | |||
| `LLM_KEY` | The name of the model you want to use | String | Currently supported llm keys: `OPENAI_GPT4_TURBO`, `OPENAI_GPT4V`, `OPENAI_GPT4O`, `OPENAI_GPT4O_MINI`, `ANTHROPIC_CLAUDE3`, `ANTHROPIC_CLAUDE3_OPUS`, `ANTHROPIC_CLAUDE3_SONNET`, `ANTHROPIC_CLAUDE3_HAIKU`, `ANTHROPIC_CLAUDE3.5_SONNET`, `BEDROCK_ANTHROPIC_CLAUDE3_OPUS`, `BEDROCK_ANTHROPIC_CLAUDE3_SONNET`, `BEDROCK_ANTHROPIC_CLAUDE3_HAIKU`, `BEDROCK_ANTHROPIC_CLAUDE3.5_SONNET`, `AZURE_OPENAI` | | |||
| `LLM_KEY` | The name of the model you want to use | String | Currently supported llm keys: `OPENAI_GPT4_TURBO`, `OPENAI_GPT4V`, `OPENAI_GPT4O`, `OPENAI_GPT4O_MINI`, `ANTHROPIC_CLAUDE3`, `ANTHROPIC_CLAUDE3_OPUS`, `ANTHROPIC_CLAUDE3_SONNET`, `ANTHROPIC_CLAUDE3_HAIKU`, `ANTHROPIC_CLAUDE3.5_SONNET`, `BEDROCK_ANTHROPIC_CLAUDE3_OPUS`, `BEDROCK_ANTHROPIC_CLAUDE3_SONNET`, `BEDROCK_ANTHROPIC_CLAUDE3_HAIKU`, `BEDROCK_ANTHROPIC_CLAUDE3.5_SONNET`, `AZURE_OPENAI`, `GEMINI_PRO`, `GEMINI_FLUSH`| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo: GEMINI_FLUSH
should be GEMINI_FLASH
for consistency with the configuration name gemini-1.5-flash
. This typo is also present in the SECONDARY_LLM_KEY
description.
Important
Add configurations for
gemini-1.5-pro
andgemini-1.5-flash
models with vision support and update README.GEMINI_PRO
configuration forgemini-1.5-pro
withsupports_vision=True
andmax_output_tokens=8192
inconfig_registry.py
.GEMINI_FLUSH
configuration forgemini-1.5-flash
withsupports_vision=True
andmax_output_tokens=8192
inconfig_registry.py
.README.md
to includeGEMINI_PRO
andGEMINI_FLUSH
in the list of supported LLM keys.This description was created by for 0aee3c2. It will automatically update as commits are pushed.