-
Notifications
You must be signed in to change notification settings - Fork 261
Update versions of llama.cpp and whisper.cpp #1874
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
Conversation
Reviewer's guide (collapsed on small PRs)Reviewer's GuideUpdates the default submodule commit references for whisper.cpp and llama.cpp in the build script to newer revisions. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
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.
Summary of Changes
Hello @rhatdan, 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 the default commit hashes for the llama.cpp
and whisper.cpp
projects within the build_llama_and_whisper.sh
script. This ensures that container images built using this script will utilize more recent versions of these critical machine learning libraries, incorporating the latest features, bug fixes, and performance improvements.
Highlights
- whisper.cpp version update: Updated the default commit hash for whisper.cpp from d0a9d8c7f8f7b91c51d77bbaa394b915f79cde6b to 7745fcf32846006128f16de429cfe1677c963b30 in the build script.
- llama.cpp version update: Updated the default commit hash for llama.cpp from 1d72c841888b9450916bdd5a9b3274da380f5b36 to 55042b3692cb1467c9ee15c62c4a9fbf180f89e3 in the build script.
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 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
-
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. ↩
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.
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.
Code Review
This pull request updates the default commit hashes for whisper.cpp
and llama.cpp
to newer versions. The changes are straightforward. My review includes suggestions to improve variable naming conventions for better consistency and adherence to shell scripting best practices, which will improve the overall maintainability of the script.
local DEFAULT_WHISPER_COMMIT="7745fcf32846006128f16de429cfe1677c963b30" | ||
local whisper_cpp_commit="${WHISPER_CPP_PULL_REF:-$DEFAULT_WHISPER_COMMIT}" |
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.
To align with shell scripting best practices (like the Google Shell Style Guide) and maintain consistency with other local variables in this script, it's recommended to use snake_case
for local variable names. I suggest renaming DEFAULT_WHISPER_COMMIT
.1
local DEFAULT_WHISPER_COMMIT="7745fcf32846006128f16de429cfe1677c963b30" | |
local whisper_cpp_commit="${WHISPER_CPP_PULL_REF:-$DEFAULT_WHISPER_COMMIT}" | |
local default_whisper_commit="7745fcf32846006128f16de429cfe1677c963b30" | |
local whisper_cpp_commit="${WHISPER_CPP_PULL_REF:-$default_whisper_commit}" |
Style Guide References
Footnotes
-
The Google Shell Style Guide recommends using lowercase with underscores for local variable names (
lower_case_with_underscores
). This improves readability and distinguishes them from global constants. ↩
local DEFAULT_LLAMA_CPP_COMMIT=55042b3692cb1467c9ee15c62c4a9fbf180f89e3 | ||
local llama_cpp_commit="${LLAMA_CPP_PULL_REF:-$DEFAULT_LLAMA_CPP_COMMIT}" |
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.
Similar to the other comment, this local variable should be renamed to snake_case
for consistency and to follow common shell scripting style conventions.1
local DEFAULT_LLAMA_CPP_COMMIT=55042b3692cb1467c9ee15c62c4a9fbf180f89e3 | |
local llama_cpp_commit="${LLAMA_CPP_PULL_REF:-$DEFAULT_LLAMA_CPP_COMMIT}" | |
local default_llama_cpp_commit=55042b3692cb1467c9ee15c62c4a9fbf180f89e3 | |
local llama_cpp_commit="${LLAMA_CPP_PULL_REF:-$default_llama_cpp_commit}" |
Style Guide References
Footnotes
-
The Google Shell Style Guide recommends using lowercase with underscores for local variable names (
lower_case_with_underscores
). This improves readability and distinguishes them from global constants. ↩
/packit rebuild-failed |
Signed-off-by: Daniel J Walsh <[email protected]>
Merging. |
Summary by Sourcery
Update default commit references for llama.cpp and whisper.cpp in the build script
Chores: