Weekly GitHub Report for Llama.cpp: May 26, 2025 - June 02, 2025 (12:07:50)
Weekly GitHub Report for Llama.cpp
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is b4991
1.2 Version Information:
The version release on March 29, 2025, introduces key updates and changes, though specific details are not provided in the given information. Notable highlights or trends cannot be identified without further context.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
As of our latest update, there are no active issues with ongoing comments this week.
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- Kompute-based Vulkan backend shows an GGML_OP_GET_ROWS error: This issue pertains to a problem with the Kompute-based Vulkan backend, which is exhibiting a GGML_OP_GET_ROWS error that does not occur with other Vulkan backends. The problem has been open for a significant duration of 427 days and 18 hours, indicating a potentially complex or unresolved technical challenge.
- Question: How to generate an MPS gputrace: This issue is about a user seeking guidance on how to generate a Metal Performance Shaders (MPS) gputrace for the llama.cpp project during model inference, as part of efforts to enhance the Metal backend for a project at Hugging Face. The user is specifically interested in obtaining a debugger output similar to what is provided by the Metal Debugger in Xcode, and is looking for any documented or known methods to achieve this.
- common: download from URL, improve parallel download progress status: This issue addresses the need to improve the progress status display for parallel downloads when retrieving sharded models, as the current implementation causes conflicts in the progression indicators. The proposed solution involves properly implementing the
CURLOPT_NOPROGRESSoption to manage the progress display more effectively during these parallel download operations. - kubernetes example: This issue is about the need for a Helm chart for the
llama.cppserver to facilitate its deployment on Kubernetes, which is a popular platform for managing containerized applications at scale. The issue has been open for over a year, and while initial work has begun, the contributor is seeking additional help from the community to advance the project. - Misc. bug: terminate called after throwing an instance of 'vk::DeviceLostError': This issue involves a bug in the llama.cpp project where running the application using Vulkan on certain laptops results in a 'vk::DeviceLostError', causing the program to terminate unexpectedly. The problem is particularly perplexing because the 'llama-bench' module operates without issues, suggesting that the error may be specific to certain configurations or command-line options used with the 'llama-cli' and 'llama-server' modules.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 0
Summarized Issues:
As of our latest update, there are no open issues for the project this week.
2.4 Closed Issues
This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.
Issues Closed This Week: 0
Summarized Issues:
As of our latest update, there were no issues closed in the project this week.
2.5 Issue Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
As of our last update, there are no open or closed issues with discussions going on within the past week.
III. Pull Requests
3.1 Open Pull Requests
This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Opened This Week: 0
As of our latest update, there are no open pull requests for the project this week.
3.2 Closed Pull Requests
This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Closed This Week: 0
As of our latest update, there are no closed pull requests for the project this week.
3.3 Pull Request Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
As of our last update, there are no open or closed pull requests with discussions going on within the past week.
IV. Contributors
4.1 Contributors
Active Contributors:
We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.
If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.
| Contributor | Commits | Pull Requests | Issues | Comments |
|---|---|---|---|---|
| ngxson | 202 | 5 | 3 | 39 |
| ggerganov | 65 | 2 | 2 | 31 |
| slaren | 52 | 0 | 1 | 45 |
| CISC | 53 | 3 | 2 | 29 |
| JohannesGaessler | 37 | 0 | 3 | 39 |
| gabe-l-hart | 48 | 3 | 1 | 1 |
| jeffbolznv | 24 | 0 | 0 | 10 |
| qnixsynapse | 17 | 5 | 0 | 11 |
| matteoserva | 16 | 0 | 3 | 3 |
| shibizhao | 18 | 1 | 1 | 2 |