Quantify Issues

Recent GitHub Issues Activity

_{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.}

Quantify commits

Quantified Commit Activity Over 30 Days

_{PRs: created by that dev and opened/merged/closed-unmerged during the period}

Report On: Fetch issues

Recent Activity Analysis

The GitHub repository for the One API project has seen considerable recent activity, with a total of 622 open issues. The latest issues predominantly revolve around bugs and enhancements related to user authentication, model integration, and API functionality. Notably, there is a recurring theme of users experiencing difficulties with model access and configuration, particularly concerning the handling of tokens and API keys.

Several issues highlight critical bugs, such as the inability to retrieve or utilize certain models effectively, leading to significant user frustration. Additionally, there are multiple requests for enhancements to improve user experience and streamline operations, indicating a demand for more robust features.

Issue Details

Most Recently Created Issues

1. Issue #1805: 忘记root密码 如何找回？

   • Priority: Bug
   • Status: Open
   • Created: 0 days ago

2. Issue #1804: root用户登录不上去，显示用户名错误或已被

   • Priority: Bug
   • Status: Open
   • Created: 1 day ago

3. Issue #1803: 支持o1模型的接入

   • Priority: Enhancement
   • Status: Open
   • Created: 1 day ago

4. Issue #1802: Enhance One-API with Langfuse: Empowering LLM Development and Monitoring

   • Priority: Enhancement
   • Status: Open
   • Created: 1 day ago

5. Issue #1801: Alex-lsky AWS Bedrock 新增llama3.1测试无法通过，报错 adaptor not found

   • Priority: Bug
   • Status: Open
   • Created: 2 days ago

Most Recently Updated Issues

1. Issue #1797: 每次的请求数据不会保存吗？

   • Priority: Enhancement
   • Status: Edited 2 days ago

2. Issue #1796: glm-4模型调用问题：调用tools中的web_search时报错

   • Priority: Bug
   • Status: Edited 4 days ago

3. Issue #1795: 请求增加FIM代码补全功能

   • Priority: Enhancement
   • Status: Edited 4 days ago

4. Issue #1794: 豆包FunctionCall无效、Usage总是为null

   • Priority: Bug
   • Status: Edited 5 days ago

5. Issue #1789: test model mapping fail

   • Priority: Bug
   • Status: Edited 9 days ago

Analysis of Notable Issues

• Several issues (#1805, #1804) regarding root password recovery indicate potential security concerns or usability challenges that could deter new users from effectively managing their accounts.
• The enhancement requests (#1803, #1802) suggest a proactive community seeking to expand the capabilities of the One API, particularly in integrating new models and improving existing functionalities.
• Bugs related to model access (#1801) highlight integration challenges that may affect user satisfaction and operational reliability.
• The ongoing discussions about request data persistence (#1797) reflect a desire for improved logging and data management features within the API.

Conclusion

The One API project is experiencing active engagement from its user base, with a mix of bug reports and enhancement requests indicating both challenges and opportunities for growth. Addressing the critical bugs while implementing requested features will be essential in maintaining user trust and satisfaction as the project evolves.

Report On: Fetch pull requests

Overview

The repository songquanpeng/one-api currently has 55 open pull requests (PRs), reflecting a vibrant development activity. The PRs cover a range of features, fixes, and enhancements aimed at improving the functionality and usability of the One API platform.

Summary of Pull Requests

1. PR #1798: feat: add siliconflow usage
   Created 3 days ago by TimeTrapzz. This PR introduces the usage of SiliconFlow in the API, with self-test verification provided. Notable changes include additions to several files related to channel billing and UI components.

2. PR #1793: fix: postgres use COALESCE replace null
   Created 7 days ago by guogeer. This fix enhances PostgreSQL handling by replacing null values with COALESCE, improving database query reliability.

3. PR #1792: Return the usage info
   Created 8 days ago by byte911. This PR addresses missing usage information in the API response, verified through self-hosted service testing.

4. PR #1790: fix: cannot test mapping model
   Created 9 days ago by guogeer. This fix resolves issues with testing mapping models, ensuring that tests run smoothly.

5. PR #1780: Update disabled channel
   Created 14 days ago by Ghostz (ye4293). This update addresses previously disabled channels, with a code coverage report indicating areas needing attention.

6. PR #1747: 修复阿里text-embedding-v2和v3向量模型永远都调用v1的问题
   Created 25 days ago by leavegee. This PR fixes an issue where specific embedding models were incorrectly routed to an older version.

7. PR #1761: fix: modify the type of token models to be text
   Created 21 days ago by 徐瑞东 (xuruidong). This change modifies the database schema for token models to prevent data truncation issues.

8. PR #1759: feat: ResponseFormat support json_schema
   Created 24 days ago by majian (majian159). This feature adds support for JSON schema in response formatting.

9. PR #1743: fix: wrong VERSION path in Dockerfile
   Created 28 days ago by Kingsley (kingsleydon). This fix corrects the Dockerfile to ensure proper versioning during builds.

10. PR #1741: feat: add lobechat open link options
    Created 29 days ago by 千寻简 (MrChihiro). This feature adds options for opening links in the Lobechat interface.

11. PR #1740: 更新阶跃星辰的模型
    Created 29 days ago by forrestlinfeng. This PR updates specific model configurations.

12. PR #1732: feat: 支持SparkDesk-v3.1-128K以及hunyuan-vision
    Created 33 days ago by lihangfu. This feature supports new model versions for enhanced performance.

13. PR #1728: fix:getTokenById return token nil, make panic
    Created 35 days ago by qinguoyi. This fix prevents panic errors when retrieving tokens with ID zero.

14. PR #1725: feat: add oidc support
    Created 36 days ago by OnEvent (Oniokey). This feature introduces OIDC login support, enhancing authentication methods available in the API.

15. PR #1721: feat: support new openai models (4o 0806, chatgpt-4o-latest)
    Created 38 days ago by TAKO (HynoR). This PR adds support for newly released OpenAI models, optimizing cost efficiency for users.

16. PR #1702: fix: ollama stream response unmarshal error
    Created 45 days ago by glc-coder (leon6002). This fix addresses unmarshalling errors in Ollama stream responses.

17. PR #1690: "add parser multipart/form-data"
    Created 52 days ago by 抒情熊 (bearslyricattack). This feature adds parsing capabilities for multipart/form-data requests.

18. PR #1666: feat: berry主题发送邮箱验证码添加loading效果和倒计时，修复多次点击导致发送多个验证码问题
    Created 57 days ago by jinjianmingming (jinjianming). Enhances email verification functionality with loading effects and prevents multiple submissions.

19. PR #1660: feat: 余额不足提示中文增强引导性
    Created 59 days ago by jinjianmingming (jinjianming). Improves user feedback for insufficient balance notifications.

20. PR #1659: feat: 引入到期时间概念,当非default的分组时将有到期时间概念
    Created 59 days ago by jinjianmingming (jinjianming). Introduces expiration concepts for user groups to manage access effectively.

Analysis of Pull Requests

The current set of pull requests reflects a dynamic development environment focused on enhancing functionality and addressing bugs within the One API project. The majority of recent PRs are aimed at fixing existing issues or adding new features that align with user needs and expectations from a multi-model AI interface management system.

Common Themes

1. Feature Enhancements: Many PRs introduce new features or improve existing functionalities, such as support for additional AI models (#1721), enhanced user feedback mechanisms (#1660), and improved email verification processes (#1666).

2. Bug Fixes: A significant number of PRs focus on resolving bugs that affect system stability and performance (#1793, #1790, #1728). These fixes are crucial as they enhance user experience and maintain system reliability.

3. Database Improvements: Several recent changes involve modifications to database schemas or queries (#1761, #1793), indicating ongoing efforts to optimize data handling and storage efficiency within the application.

4. User Management Features: The introduction of OIDC support (#1725) and enhancements to user group management (#1659) suggest a strategic focus on improving authentication and authorization processes, which are vital for security in multi-user environments.

Anomalies

• The presence of multiple open PRs from the same contributors indicates a collaborative environment but may also point towards potential bottlenecks if not managed effectively.
• Some PRs have raised concerns regarding code coverage and testing adequacy (#1780, #1759), highlighting a need for improved testing practices to ensure robustness before merging changes into the main branch.
• There are indications of disputes or differing opinions on implementation details within comments on some PRs (#1725), which could lead to delays in merging if not addressed constructively.

Lack of Merge Activity

Despite a high volume of open PRs, there appears to be a delay in merging some contributions into the main branch, particularly those that have been open for several weeks or longer (#1747, #1702). Addressing this backlog should be prioritized to maintain momentum in development and encourage continued community engagement.

Conclusion

Overall, the active pull request landscape showcases a commitment to continuous improvement within the One API project while also revealing areas that require attention—particularly around testing practices and merge management—to ensure that development remains efficient and responsive to user needs.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members and Their Recent Activities

1. longkeyy

   • Recent commits include synchronization with the official release of the groq model and updates to the gemini model and pricing.

2. TAKO (HynoR)

   • Added a new Cloudflare free model (Llama 3.1 8b) and supported gpt-4o mini.

3. MotorBottle

   • Implemented max tokens and context window setting options for the Ollama channel, enhancing data processing logic.

4. SLKun

   • Updated the Ollama embedding API to support multi-text embedding.

5. Shenghang Tsai (jackalcooper)

   • Introduced SiliconFlow and made multiple updates to README files and constants.

6. Junyan Qin (RockChinQ)

   • Updated documentation for QChatGPT.

7. Laisky.Cai (Laisky)

   • Added Proxy channel type and relay mode; also worked on various bug fixes related to vertexai and improved headers for anthropic.

8. zijiren (zijiren233)

   • Contributed to multiple features including fast building for linux/arm64 frontend, vertexai support, and various bug fixes.

9. igophper

   • Focused on fixing embedding models for doubao and other issues related to image generation.

10. JustSong (songquanpeng)

    • Involved in numerous commits addressing CI issues, improving documentation, fixing bugs across various functionalities, and enhancing user experience through feature additions.

11. F1ynn Zhan9 (f1ynn-zhan9)

    • Added a field stop in GeneralOpenAIRequest.

12. LiuVaayne (vaayne)

    • Supported Claude and Gemini in Vertex AI with several fixes.

13. Ghostz (ye4293)

    • Worked on text field checks for requests and fixed issues related to image generation.

14. Qiying Wang (WqyJh)

    • Contributed features supporting gpt-4o and refactored components for better compatibility with AWS Claude.

15. Mikey (dirname)

    • Added tool support for AWS & Claude.

16. Leo Q (LeoQuote)

    • Engaged in CI improvements, documentation updates, and feature enhancements related to UI themes.

17. Shi Jilin (shijilin0116)

    • Supported Spark4.0 Ultra with various bug fixes.

18. lihangfu

    • Focused on supporting Spark4.0 Ultra and contributed to other enhancements.

19. Darkside (da730)

    • Updated documentation related to related projects.

20. Jason (jasonhp)

    • Added Novita AI as a model provider.

Patterns, Themes, and Conclusions

• The team has been actively contributing to both feature enhancements and bug fixes, with a significant focus on improving the integration of various AI models.
• Collaboration is evident among team members, as many commits are co-authored or involve multiple contributors working on related features.
• There is a strong emphasis on documentation updates alongside code changes, indicating an awareness of the importance of maintaining clear project guidelines.
• The recent activity suggests ongoing development efforts to address a high number of open issues (677), which could imply that while new features are being added, there is also a need for stabilization.
• The presence of multiple contributors working on similar areas indicates a collaborative environment aimed at rapid iteration and improvement of the project.
• Overall, the development team appears focused on enhancing functionality while ensuring that existing features are stable and well-documented, reflecting a commitment to quality in their software development practices.