The Phi-3 Cookbook project, a resource for Microsoft's advanced small language models, has seen minimal development activity recently, with a focus on documentation and dependency updates.
The Phi-3 Cookbook aims to assist users in utilizing Microsoft's Phi-3 models, known for their performance in language processing and reasoning tasks.
Recent issues and pull requests (PRs) indicate ongoing challenges with documentation clarity and model usage. Key issues include user confusion about model parameters (#198) and critical bugs related to tool integration (#196). PRs have focused on fixing documentation (#186) and updating dependencies (#194, #193, #192).
Kinfey (kinfey)
Dependabot[bot]
Lee Stott (leestott)
Ikko Eltociear Ashimine (eltociear)
Minseok Song (skytin1004)
El Bruno (elbruno)
Nicholas King (nking-1)
Documentation Confusion: Persistent issues with unclear documentation (#198), affecting user experience.
Critical Bug: Unhandled exception related to tool support (#196), posing significant user challenges.
Multi-Language Support: Efforts to enhance accessibility with translations in multiple languages (#195).
Dependency Management: Regular updates via Dependabot ensure security and compatibility.
Community Engagement: Active participation in resolving issues and contributing translations highlights community involvement.
| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 3 | 2 | 4 | 3 | 1 |
| 30 Days | 12 | 7 | 25 | 12 | 1 |
| 90 Days | 54 | 43 | 172 | 39 | 1 |
| All Time | 64 | 50 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
| Developer | Avatar | Branches | PRs | Commits | Files | Changes |
|---|---|---|---|---|---|---|
| Ikko Eltociear Ashimine |  |
1 | 1/1/0 | 13 | 98 | 12472 |
| Kinfey |  |
1 | 2/2/0 | 3 | 52 | 7654 |
| dependabot[bot] |  |
1 | 12/11/1 | 11 | 14 | 589 |
| El Bruno |  |
1 | 1/1/0 | 5 | 22 | 196 |
| Minseok Song |  |
1 | 2/1/0 | 5 | 6 | 84 |
| Lee Stott |  |
1 | 3/3/0 | 11 | 8 | 36 |
| Nicholas King |  |
1 | 1/1/0 | 1 | 1 | 2 |
| None (topce) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Yu-Ting Chen (yuting1008) | 0 | 1/0/0 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The recent activity on the Phi-3CookBook GitHub repository shows a total of 14 open issues, with the most recent being created just today. There are several notable issues that highlight user confusion regarding documentation and functionality, particularly around model usage and error handling.
A recurring theme among the open issues is the lack of clarity in documentation, especially concerning the expected behavior of model parameters and configurations. Users frequently report errors related to model inference and fine-tuning, indicating potential gaps in the guidance provided for these processes.
Issue #198: 'About' section of repository is confusing
Issue #196: Unhandled exception. System.ClientModel.ClientResultException: HTTP 400 (api_error: ) phi3.5 does not support tools
Issue #187: Converting Phi-3.5-vision-instruct to onnx format fails
Issue #185: Wrong LoRA tuning example
Issue #183: Lora fine tuning phi-3.5 moe
Issue #172: Multi turn conversation | Phi3.5 vision
Issue #153: SK + Phi-3-vision-128k-instruct-onnx-cpu => Not getting Results
Issue #138: RAG for phi 3 vision using kernel memory
The issues reflect a range of challenges users face, particularly in understanding how to properly configure and utilize the Phi-3 models:
The confusion in the 'About' section (#198) suggests that new users may struggle to grasp the project's purpose and usage.
The unhandled exception in issue #196 indicates a critical bug that could hinder user experience significantly, especially for those relying on tools integration.
Issues regarding ONNX conversion (#187) and incorrect examples for LoRA tuning (#185) point to potential gaps in documentation or updates that have not been reflected in the examples provided.
The multi-turn conversation issue (#172) highlights a need for clearer guidance on using the models effectively in conversational contexts.
Overall, there appears to be a strong demand for improved documentation and clearer examples to help users navigate common pitfalls when working with the Phi-3 models.
| Issue Number | Title | Priority | Status | Created | Updated |
|---|---|---|---|---|---|
| #198 | 'About' section of repository is confusing | Low | Open | Today | N/A |
| #196 | Unhandled exception... phi3.5 does not support tools | High | Open | 2 days ago | 1 day ago |
| #187 | Converting Phi-3.5-vision-instruct to onnx format fails | Medium | Open | 7 days ago | 3 days ago |
| #185 | Wrong LoRA tuning example | Medium | Open | 9 days ago | N/A |
| #183 | Lora fine tuning phi-3.5 moe | Medium | Open | 13 days ago | 4 days ago |
| #172 | Multi turn conversation | Phi3.5 vision | Medium | 22 days ago | 2 days ago |
| #153 | SK + Phi-3-vision-128k-instruct-onnx-cpu => Not getting Results | Medium | Open | 32 days ago | 4 days ago |
| #138 | RAG for phi 3 vision using kernel memory | Low | Open | 40 days ago | 3 days ago |
This summary provides an overview of current issues affecting user experience and highlights areas where documentation improvements are needed to facilitate better understanding and usage of the Phi-3 models.
The analysis of the pull requests (PRs) in the Phi-3 Cookbook repository reveals a dynamic and active development environment. The project is focused on enhancing the functionality, documentation, and accessibility of Microsoft's Phi-3 models, which are advanced small language models (SLMs). The PRs indicate ongoing efforts to improve multi-language support, update dependencies, refine documentation, and expand the range of examples and tutorials available to users.
The pull requests reflect several key themes in the development of the Phi-3 Cookbook:
Continuous Improvement and Maintenance: The regular updates to dependencies (e.g., PRs #194, #193, #192) indicate a commitment to maintaining the project's health and security. This is crucial for projects that rely on external libraries and tools, as it helps prevent vulnerabilities and ensures compatibility with new features.
Enhancing Accessibility and Usability: PRs like #195 demonstrate an effort to make the project more accessible to a global audience by providing translations in multiple languages. This is particularly important for open-source projects that aim to reach a diverse user base.
Documentation and Clarity: Several PRs focus on improving documentation (e.g., PRs #186, #197). Clear and accurate documentation is essential for user adoption and satisfaction, especially for complex projects involving advanced technologies like AI models.
Community Engagement: The active participation in updating translations and fixing bugs suggests a responsive community that contributes to the project's growth. This is further supported by the project's engagement with contributors through platforms like Discord.
Focus on Practical Applications: The inclusion of end-to-end samples (e.g., PRs related to E2E samples) highlights an emphasis on practical applications of Phi-3 models. This approach not only showcases the models' capabilities but also provides users with valuable resources to implement similar solutions.
In conclusion, the Phi-3 Cookbook is characterized by active development focused on enhancing its functionality, accessibility, and usability through regular updates, community contributions, and a strong emphasis on practical applications of its underlying technologies.
Kinfey (kinfey)
Summary
Quantified Reports
Detailed Reportsphi3ext and rag_webgpu_chat directories.Dependabot[bot]
webpack, express, body-parser) in various directories.Lee Stott (leestott)
Ikko Eltociear Ashimine (eltociear)
Minseok Song (skytin1004)
El Bruno (elbruno)
Nicholas King (nking-1)
Others:
topce and yuting1008 have no recent activity reported.The recent activities indicate a well-coordinated effort among team members to enhance the Phi-3 Cookbook repository's functionality and usability. The combination of manual contributions and automated dependency management suggests a robust development process aimed at maintaining high-quality standards in documentation and code integrity.