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

Developer	Avatar	Branches	PRs	Commits	Files	Changes
Minura Punchihewa		5	9/9/0	40	54	3378
Zoran Pandovski		3	13/13/1	15	17	1280
Andrey		5	14/11/0	19	32	1129
martyna-mindsdb		1	12/17/0	17	27	621
None (dependabot[bot])		6	7/0/2	6	3	368
Dylan Ketterer (dylanketterer)		1	1/0/0	2	4	238
Max Stepanov		2	6/7/0	9	9	153
Ty		3	3/3/0	13	9	139
Daniel Usvyat		2	2/1/0	2	4	65
Hamish Fagg		1	2/2/0	2	1	55
AverellGatton		1	0/0/0	1	2	13
Guspan Tanadi		1	1/1/0	1	1	2
Lucas Koontz		1	1/1/0	1	1	1
Parthiv Makwana (parthiv11)		0	2/0/0	0	0	0
Anudeep Adiraju (anudeepadi)		0	1/0/0	0	0	0
Ethan Steininger (esteininger)		0	1/0/0	0	0	0
Mohamed Abderrahim (mabderrahim)		0	1/0/0	0	0	0
Talaat Hasanin (TalaatHasanin)		0	1/0/0	0	0	0
Panos Kyriakis (panoskyriakis)		0	1/0/0	0	0	0
Prajwal Pai (prajwal-pai77)		0	1/0/0	0	0	0
Deepanshu Jha (Prog-Deepanshu)		0	1/0/1	0	0	0

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

Report On: Fetch issues

Recent Activity Analysis

The MindsDB GitHub repository shows a high level of recent activity, with 106 open issues. Notably, there are multiple bug reports related to integration issues, particularly with the OpenAI and LangChain handlers, indicating potential instability in these areas. Themes of user frustration are evident, especially regarding installation problems and error messages that lack clarity. The community appears actively engaged in troubleshooting and reporting issues, which may suggest a need for improved documentation and support.

Issue Details

Recent Issues

1. Issue #9724: [Integration]: Google Cloud Storage Integration

   • Priority: Enhancement
   • Status: Open
   • Created: 4 days ago
   • Updated: 3 days ago

2. Issue #9716: [Bug]: OpenAI models (in conversational mode) should not require prompt

   • Priority: Bug
   • Status: Open
   • Created: 7 days ago
   • Updated: 6 days ago

3. Issue #9714: [Bug]: LiteLLM handler not handling queries properly

   • Priority: Bug
   • Status: Open
   • Created: 7 days ago
   • Updated: 6 days ago

4. Issue #9710: [Bug]: LangChain handler issue with OpenAI API key

   • Priority: Bug
   • Status: Open
   • Created: 8 days ago
   • Updated: 7 days ago

5. Issue #9702: [Bug]: Fix Couchbase

   • Priority: Bug
   • Status: Open
   • Created: 10 days ago
   • Updated: 9 days ago

Notable Patterns and Anomalies:

• A significant number of recent issues (especially bugs) pertain to integrations with popular AI tools like OpenAI and LangChain, suggesting these components may require urgent attention.
• Users report confusion and errors when using the conversational mode for models, indicating potential gaps in functionality or documentation.
• The presence of multiple unresolved bugs related to integrations raises concerns about the stability of the platform.

Important Themes:

• Integration Issues: Several issues revolve around failures in integrating with external services (e.g., OpenAI, LiteLLM).
• Documentation Gaps: Users frequently express confusion regarding error messages and expected behaviors, highlighting a need for clearer guidance.
• Community Engagement: Active discussions indicate a responsive community that seeks to address issues collaboratively.

Summary of Issues:

The current state of open issues reflects a mix of enhancement requests and critical bugs primarily associated with integrations. The ongoing dialogue within the community suggests that while users are engaged, there is an urgent need for improvements in both functionality and documentation to enhance user experience.

Report On: Fetch pull requests

Overview

The analysis of the MindsDB repository's pull requests (PRs) reveals a dynamic and active development environment. The PRs cover a wide range of enhancements, bug fixes, integrations with various data sources, and improvements to existing functionalities. The community engagement is evident from the number of contributions addressing both new features and critical issues.

Summary of Pull Requests

1. PR #9744: Upgrade mintlify to latest

   • Upgrades the mintlify package to its latest version, ensuring documentation is up-to-date with the latest features and fixes.

2. PR #9743: Bump send and express in /docs

   • Updates dependencies for send and express, which are crucial for handling HTTP requests and responses in documentation.

3. PR #9742: Bump serve-static and express in /docs

   • Similar to PR #9743, this PR updates serve-static and express, focusing on serving static files efficiently.

4. PR #9740: Bump body-parser and express in /docs

   • Updates body-parser and express, enhancing the ability to parse incoming request bodies.

5. PR #9739: Bump path-to-regexp and express in /docs

   • Updates path-to-regexp and express, improving routing capabilities within the documentation.

6. PR #9738: Bump litellm from 1.40.16 to 1.44.8 in /mindsdb/integrations/handlers/litellm_handler

   • Upgrades the litellm package, enhancing integration with MindsDB's AI capabilities.

7. PR #9737: Refactor SQL toolkit descriptions for clarity and usability

   • Improves documentation clarity for SQL toolkits, making it easier for users to understand how to use them effectively.

8. PR #9732: Slack Integration Fixes: Pagination for Channels and Handling App Mentions

   • Fixes issues with Slack integration by adding pagination for channels and improving message handling logic.

9. PR #9731: LLM function

   • Introduces a new function for large language models (LLMs), expanding MindsDB's AI capabilities.

10. PR #9730: Bump langchain from 0.1.11 to 0.2.10 in /requirements

    • Updates langchain, a library for building applications powered by language models, ensuring compatibility with MindsDB's latest features.

11. PR #9727: Unify AI integration

    • Adds support for Unify AI, allowing MindsDB users to access various AI models with a single API key.

12. PR #9726: Google Cloud Storage Integration

    • Implements integration with Google Cloud Storage, enabling seamless data management within MindsDB.

13. PR #9725: Encrypt handler credentials

    • Enhances security by encrypting handler credentials, protecting sensitive information from unauthorized access.

14. PR #9721: Fix Teams: don't connect when handler files are imported

    • Fixes an issue with Microsoft Teams integration where handlers would attempt to connect when imported without proper configuration.

15. PR #9719: SAP Hana Integration Improvements

    • Improves SAP Hana integration, making it more robust and enterprise-ready.

16. PR #9715: GPU support for huggingface

    • Adds GPU support for Hugging Face models, significantly improving performance for AI tasks.

17. PR #9712: Adding S3 Data Source for Knowledge Base

    • Integrates S3 as a data source for knowledge bases, expanding MindsDB's data ingestion capabilities.

18. PR #9705: Changes in encryption functions

    • Modifies encryption functions to improve security and usability across MindsDB integrations.

19. PR #9703: Update sdk & minor changes to connection of cluster

    • Updates SDK versions and minor connection adjustments for Couchbase integration.

20. PR #9700: Added a Check for Directory Path Traversal

    • Adds security checks against directory path traversal vulnerabilities when accessing server resources.

21. PR #9688: OpenBB bug API KEY Fix

    • Fixes an issue with OpenBB integration related to API key handling.

22. PR #9654: Added Prometheus Handler

    • Introduces a new handler for fetching data from Prometheus servers, enhancing monitoring capabilities within MindsDB.

23. PR #9599: Mindsdb starting speedup, part 2

    • Implements optimizations to reduce startup time by avoiding unnecessary imports and preheating processes.

24. PR #9427: [Integration] Financial Modeling Prep Api Integration

    • Integrates Financial Modeling Prep API, providing users access to financial data directly through MindsDB.

25. PR #9381: [Integration]: Serpstack api integration

    • Adds integration with Serpstack API, enabling web scraping capabilities within MindsDB applications.

26. PR #9131: [Integration]: Fireworks ai Integration

    • Integrates Fireworks.ai into MindsDB, expanding its AI service offerings.

27. PR #9686: [Docs]: Add instructions for enabling basic authentication

    • Updates documentation to include instructions on enabling basic authentication for REST APIs in MindsDB.

28. PR #9684: Create mixpeek.mdx

    • Introduces integration between MindsDB and Mixpeek Embed, allowing advanced video understanding capabilities like indexing and semantic searches on video content.

29. PR #9683: Don't Automatically Convert KB Name to Lower Case During Creation

    • Addresses an issue where knowledge base names were automatically converted to lower case, causing confusion and potential errors in retrieval operations.

30. PR #9672: Add pgvector Logging When Connecting

    • Adds logging capabilities during pgvector connections, aiding debugging efforts related to vector database integrations.

31. PR #9641: Portkey AI Gateway integration

    • Integrates Portkey AI Gateway into MindsDB, providing users access to additional AI models through a unified API key system.

32. PR #9619: Upgrade Litellm version

    • Upgrades Litellm version used in langchain integrations, enhancing performance and compatibility with newer models.

33-34 are closed PRs that were superseded or not merged due to various reasons such as being addressed by other PRs or conflicts that were resolved differently.

35-36 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

37-38 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

39-40 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

41-42 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

43-44 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

45-46 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

47-48 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

49-50 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

51-52 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

53-54 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

55-56 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

57-58 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

59-60 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

61-62 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

63-64 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

65-66 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

67-68 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

69-70 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

71-72 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

73-74 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

75-76 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

77-78 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

79-80 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

81-82 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

83-84 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

85-86 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

87-88 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

89-90 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

91-92 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

93-94 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

95-96 are closed PRs that were merged successfully after addressing review comments or making necessary adjustments.

Report On: Fetch commits

Repo Commits Analysis

Development Team and Recent Activity

Team Members and Recent Contributions

1. Max Stepanov (StpMax)

   • Recent Activity:
   • Implemented an option to check connection for GET /database endpoint.
   • Set pymongo requirement to version 4.8.0.
   • Fixed BYOM model creation.
   • Contributed to the removal of obsolete parameters from the chatbot via Slack/MS Teams.

2. Zoran Pandovski (ZoranPandovski)

   • Recent Activity:
   • Bumped version in __about__.py.
   • Updated CLA and released new versions.
   • Contributed to various documentation updates.

3. Andrey (ea-rus)

   • Recent Activity:
   • Fixed issues in ray server handler and table info fetching.
   • Worked on integration improvements for multiple handlers including qdrant and vector handlers.
   • Added a created_at field to skills response.

4. Minura Punchihewa (MinuraPunchihewa)

   • Recent Activity:
   • Made extensive updates across multiple integrations including IBM DB2, Teradata, and MS Teams.
   • Improved documentation for various integrations.
   • Implemented caching mechanisms in Slack handler.

5. Martyna (martyna-mindsdb)

   • Recent Activity:
   • Updated documentation for OpenAI and Microsoft Teams integrations.
   • Removed obsolete parameters from chatbot documentation.
   • Added FAQs and improved various integration docs.

6. Lucas Koontz (lucas-koontz)

   • Recent Activity:
   • Added a created_at field to skills response.

7. Daniel Usvyat (dusvyat)

   • Recent Activity:
   • Extracted generated query into response and made improvements to SQL toolkit descriptions.

8. Hamish Fagg (hamishfagg)

   • Recent Activity:
   • Worked on fixes related to Docker builds and CI/CD processes.

9. Ty (tmichaeldb)

   • Recent Activity:
   • Implemented features related to agent completions and logging improvements.

10. Dependabot[bot]

    • Recent Activity:
    • Managed dependency updates across various libraries.

Patterns, Themes, and Conclusions

• Active Development: The team is actively working on both feature enhancements and bug fixes, with a significant number of commits in the last few days across multiple branches.

• Collaborative Efforts: Several members are collaborating on integration improvements, particularly with external services like MS Teams, IBM DB2, and Teradata.

• Documentation Focus: There is a strong emphasis on updating documentation alongside code changes, indicating a commitment to maintain clarity for users.

• Diverse Contributions: Contributions span various areas including backend improvements, integration enhancements, documentation updates, and dependency management, showcasing the team's versatility.

• Frequent Releases: The team has been releasing new versions regularly, suggesting a robust release cycle that keeps the project up-to-date with user needs and technical advancements.

Overall, the MindsDB development team demonstrates high engagement with ongoing contributions that enhance both functionality and user experience within the platform.