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

Rate pull requests

PR#530 - feat(webSearchPrompt): Add prompt for optimizing language typesopen

2_/5

Hyungjin Cha (hacking-racoon)Created: 2024-12-24

The pull request introduces a minor change to the web search prompt by adding a single line that handles multilingual input. While the idea of processing questions in their original language when relevant is beneficial, the implementation is minimal and lacks depth. The change is not significant enough to warrant a higher rating, as it involves only a slight modification to an existing prompt without addressing potential complexities or providing substantial improvements. Additionally, there is no evidence of testing or consideration of edge cases, which are critical for ensuring robustness in multilingual processing.

[+] Read More

PR#414 - feat: converts system prompts in markdown formatopen

3_/5

Adosh Singh (AdoshSingh)Created: 2024-10-18

The pull request converts system prompts into markdown format, which is a minor yet useful improvement for consistency and readability. However, it lacks significant impact or complexity, involving mostly formatting changes across several files. The change is straightforward with no apparent flaws, but it doesn't introduce substantial new functionality or improvements. Therefore, it merits an average rating of 3.

[+] Read More

PR#456 - Added ollama model configs to config.toml and some QOL stuffopen

3_/5

Patrick Wiltrout (vorktanamobay)Created: 2024-11-08

The pull request introduces configuration options for the Ollama model parameters and improves the user interface by sorting dropdowns. These changes are functional and improve usability, but they are relatively minor in scope and complexity. The code changes are straightforward and do not introduce any significant new functionality or complexity. The PR is well-structured but lacks significant impact or innovation, making it an average contribution.

[+] Read More

PR#512 - fix build erroropen

3_/5

Tong Li (litongjava)Created: 2024-12-09

The pull request addresses a build error by making changes to the code and dependencies. It updates error handling in the server setup, modifies UI components, and switches from Yarn to pnpm for package management. While these changes are necessary for fixing the build and improving error logging, they are mostly routine updates and not particularly significant or innovative. The PR does not introduce any new features or major improvements, hence it is rated as average.

[+] Read More

PR#444 - Fix: Enter key interrupts IME composition in MessageInput componentopen

4_/5

MJ (minai621)Created: 2024-10-30

This pull request addresses a specific and significant bug affecting users who rely on IME for typing in languages like Korean, Chinese, or Japanese. The solution is straightforward and involves adding composition event handlers to manage the IME composition state effectively. The changes are minimal yet impactful, with only a few lines of code added to handle the issue. The PR is well-documented, tested locally, and follows code formatting standards. However, it lacks extensive testing details or broader impact analysis, which prevents it from being rated as exemplary.

[+] Read More

PR#465 - 🔐 Reduce Docker size by half + improve securityopen

4_/5

Damien Laureaux (timoa)Created: 2024-11-14

The pull request significantly optimizes the Docker setup by reducing image sizes by over 60% and enhancing security through non-root user execution. It introduces multi-stage builds, improved caching, and a more standard directory structure, which are all best practices in Docker usage. The PR also updates Node to v22, aligning with current standards. However, it leaves unresolved issues with environment variables and requires manual intervention for certain configurations, which slightly detracts from its overall effectiveness. Despite these minor shortcomings, the PR represents a substantial improvement in both performance and security.

[+] Read More

PR#507 - Support deepinfra as a service provideropen

4_/5

Martin Chang (marty1885)Created: 2024-12-06

The pull request introduces a new service provider, DeepInfra, to the project, which enhances its functionality by offering an alternative for embeddings without local execution. The implementation is thorough, with changes across multiple files to integrate DeepInfra seamlessly. The code quality appears high with no obvious bugs, and the addition is significant as it provides users with free credits for embeddings. However, the PR could be improved by including more documentation or tests to ensure robustness and ease of understanding for future contributors.

[+] Read More

PR#520 - feat(ui): changed Markdown rendering libraryopen

4_/5

minicx (loss-and-quick)Created: 2024-12-13

The pull request effectively addresses a critical issue by replacing a buggy Markdown library with a more stable and extensible alternative, 'react-markdown'. It also enhances user experience by adding syntax highlighting for code blocks. The changes are well-documented, and the rationale is clear, focusing on improved reliability and future extensibility. However, it lacks the inclusion of 'remark-gfm' for full Markdown feature support, as noted in the comments. This oversight prevents it from being rated as exemplary.

[+] Read More

PR#543 - fix(ui): better handling the ui in case of errors connecting with bac…open

4_/5

Eren Yeager (asifrahaman13)Created: 2024-12-30

The pull request addresses a significant issue by improving error handling in the UI when backend connection errors occur, which enhances user experience. Additionally, it migrates from the fetch API to axios, which is a more robust solution for handling HTTP requests and errors. The changes are well-contained within a single file and are clearly aimed at improving functionality without introducing unnecessary complexity. However, the PR could have included more comprehensive testing or documentation to achieve a higher rating.

[+] Read More

PR#556 - Feature/ci cdopen

4_/5

Eli Grinfeld, MBA (eligrinfeld)Created: 2025-01-05

The pull request #556 introduces a comprehensive CI/CD workflow to the project, which is a significant enhancement. It includes automated tests, code formatting checks, test coverage reports, and deployment configurations, all of which are crucial for maintaining code quality and ensuring reliable deployments. The PR also involves substantial changes across various components of the project, including frontend setup with Tailwind CSS, server initialization improvements, and database schema updates. However, the description could be more detailed to clarify the purpose and impact of these changes, as indicated by a comment from another contributor. Overall, this PR is quite good but lacks in communication clarity.

[+] Read More

Quantify commits

Quantified Commit Activity Over 14 Days

Developer	Avatar	Branches	PRs	Commits	Files	Changes
realies		1	2/1/1	1	1	102
ItzCrazyKns		1	0/0/0	6	2	57
Sainadh Devireddy		1	0/0/0	1	1	4
Mitch Ross (mitchross)		0	1/0/1	0	0	0
Sainadh Devireddy (sainadh-d)		0	1/2/0	0	0	0
None (ProjectMoon)		0	0/0/1	0	0	0
Eli Grinfeld, MBA (eligrinfeld)		0	1/0/0	0	0	0
Eren Yeager (asifrahaman13)		0	1/0/0	0	0	0
Hyungjin Cha (hacking-racoon)		0	0/1/0	0	0	0
None (yassinesmartly)		0	1/0/1	0	0	0

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

Quantify risks

Project Risk Ratings

Report On: Fetch issues

Recent Activity Analysis

Recent GitHub issue activity for the Perplexica project shows a mix of bug reports, feature requests, and user inquiries. There is a notable focus on installation issues, particularly with Docker, and challenges with setting up and configuring the software. Users have reported problems with accessing Perplexica across networks, encountering errors during Docker builds, and difficulties in integrating with specific models or APIs like Ollama and OpenAI.

Several issues highlight the need for better documentation or support for specific configurations, such as running behind a reverse proxy or using alternative LLM providers. There are also requests for enhancements like improved language support, additional API endpoints, and better handling of search results.

Notable Issues

• #540: Reports that only the title of web pages is sent to the LLM, indicating potential issues with content retrieval.
• #536: Highlights problems with environment variables not being respected, affecting network accessibility.
• #535: Describes difficulties in connecting to Ollama despite correct configurations.
• #533: Discusses connection issues in recent Docker images, affecting functionality.
• #528: Requests integration with Kagi as a search provider, reflecting user interest in diverse search engine options.

Themes and Commonalities

• Installation and Configuration: Many users face challenges during setup, especially when using Docker. Issues often relate to network configurations, port conflicts, and environment variable settings.
• Integration with External Services: There is significant interest in integrating Perplexica with various LLM providers like Ollama and OpenAI. Users seek flexibility in configuring API endpoints and authentication mechanisms.
• Feature Enhancements: Requests for new features include improved language handling, support for additional search engines, and enhanced API capabilities.
• User Experience: Some issues focus on improving the user interface and experience, such as making settings accessible on mobile devices or providing more intuitive controls.

Issue Details

Most Recently Created Issues

1. #560: [FR] Deep Research mode

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

2. #553: balanced requests do not load

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

3. #550: server-side settings mode

   • Priority: Enhancement
   • Status: Open
   • Created 8 days ago

Most Recently Updated Issues

1. #558: Settings gear icon on mobile

   • Priority: Bug
   • Status: Closed
   • Updated 1 day ago

2. #544: Perplexica can't connect to server - Ollama running in docker container

   • Priority: Bug
   • Status: Closed
   • Updated 7 days ago

3. #540: Only the title of the web page is sent to the LLM.

   • Priority: Bug
   • Status: Closed
   • Updated 7 days ago

These issues reflect ongoing efforts to address user-reported problems and enhance the functionality of Perplexica. The project's active maintenance is evident from the frequent updates and resolutions provided by contributors.

Report On: Fetch pull requests

Analysis of Pull Requests for ItzCrazyKns/Perplexica

Open Pull Requests

Notable Open PRs

1. #556: Feature/ci cd

   • Summary: Introduces a CI/CD workflow with GitHub Actions, test environment setup, and deployment configurations.
   • Concerns: The initial description was unclear to the repository owner, indicating a need for better communication or documentation in the PR.
   • Impact: Significant as it enhances the development workflow by automating testing, building, and deployment.

2. #465: 🔐 Reduce Docker size by half + improve security

   • Summary: Optimizes Dockerfiles to reduce image size and improve security by running as a non-root user.
   • Comments: There are ongoing discussions about environment variable handling and potential conflicts.
   • Impact: Important for improving resource efficiency and security in deployment environments.

3. #512: fix build error

   • Summary: Addresses build errors by modifying UI components and switching to pnpm.
   • Concerns: This PR has been open for 35 days, indicating potential unresolved issues or lack of attention.
   • Impact: Critical if the build errors are affecting other contributors or deployments.

4. #530: feat(webSearchPrompt): Add prompt for optimizing language types

   • Summary: Proposes a method to handle multilingual queries more effectively.
   • Impact: Enhances user experience by processing queries in their original language when relevant.

5. #520: feat(ui): changed Markdown rendering library

   • Summary: Switches Markdown rendering library to react-markdown for improved reliability.
   • Comments: A reviewer suggested additional plugins for better functionality.
   • Impact: Improves UI stability and extensibility.

General Observations

• Several PRs focus on improving infrastructure (e.g., Docker optimizations, CI/CD workflows) which are crucial for long-term project sustainability.
• Some PRs have been open for extended periods (e.g., #512), which might indicate bottlenecks in review processes or complex issues needing resolution.

Closed Pull Requests

Notable Closed PRs

1. #555: fix(ws-error): add exponential reconnect mechanism

   • Summary: Implements an exponential reconnect mechanism for WebSockets to handle connection drops gracefully.
   • Outcome: Merged successfully, enhancing application robustness against network issues.

2. #548: Only Page Title is being sent to LLM

   • Summary: Fixes a logic error where only page titles were sent to the LLM instead of full content.
   • Outcome: Merged quickly, resolving a critical bug affecting search accuracy.

3. #538: [bug-fix] Delete msgs only belonging to the chat

   • Summary: Corrects message deletion logic to ensure only messages from the current chat are deleted.
   • Outcome: Merged, fixing a significant issue with chat history management.

4. #523 & #519 (Updates on Model Support)

   • These PRs update available models from providers like Groq and Anthropic, ensuring that Perplexica remains compatible with the latest AI models.

General Observations

• Several closed PRs address critical bugs and enhancements that directly impact user experience and application stability.
• The project shows active maintenance with regular merges of fixes and improvements, reflecting a healthy development pace.

Conclusion

The Perplexica project is actively evolving with significant contributions aimed at improving both infrastructure and user-facing features. However, some open PRs require attention to avoid stagnation. The closed PRs demonstrate effective issue resolution and feature enhancement, contributing positively to the project's robustness and functionality. Overall, maintaining clear communication in PR descriptions and ensuring timely reviews will further streamline development processes.

Report On: Fetch Files For Assessment

Analysis of Source Code Files

1. ui/components/ChatWindow.tsx

Structure and Quality

• Component Structure: The ChatWindow component is well-structured, with clear separation of concerns. It uses hooks like useState, useEffect, and custom hooks (useSocket) to manage state and side effects.
• WebSocket Management: The WebSocket connection is handled robustly with reconnection logic and error handling. The use of useRef for managing WebSocket instances and retry counts is appropriate.
• State Management: State variables are clearly defined and used effectively to manage the component's behavior, such as connection status, message loading, and chat history.
• Error Handling: Errors in fetching models or WebSocket connections are communicated to the user using toast notifications, which enhances user experience.
• Code Readability: The code is generally readable with descriptive variable names and inline comments that explain complex logic.
• Performance Considerations: The use of local storage for model configurations and the efficient handling of WebSocket events indicate good performance considerations.

Areas for Improvement

• Code Duplication: There are repeated patterns in setting up model providers and handling local storage, which could be refactored into utility functions to reduce duplication.
• Type Safety: While TypeScript is used, some areas could benefit from stricter type definitions, especially when dealing with external data (e.g., API responses).
• Complexity: The component has grown quite large (704 lines), which might affect maintainability. Consider breaking down into smaller sub-components where feasible.

2. ui/components/SearchVideos.tsx

Structure and Quality

• Component Functionality: This component handles video search functionality, including fetching videos based on a query and displaying them in a grid layout.
• UI Interactions: User interactions are managed through state variables like loading, open, and currentIndex, providing a responsive UI experience.
• Lightbox Integration: The integration with the yet-another-react-lightbox library is done cleanly, allowing users to view videos in a modal format.
• Code Organization: The code is organized logically, with asynchronous operations clearly separated from rendering logic.

Areas for Improvement

• Error Handling: There is no explicit error handling for the fetch operation. Adding error handling would improve robustness.
• Type Definitions: The Video type is well-defined, but further type annotations could enhance clarity, especially for API responses.
• Code Duplication: Similar logic for rendering video thumbnails could be abstracted into a separate function or component to reduce repetition.

3. src/websocket/messageHandler.ts

Structure and Quality

• Event Handling: The file effectively uses an event-driven architecture to handle WebSocket messages, leveraging Node.js's EventEmitter.
• Database Operations: Interactions with the database are performed using a clear schema definition (messagesSchema), ensuring consistency in data operations.
• Error Handling: Errors during message processing are captured and communicated back through WebSocket messages, maintaining transparency in communication.

Areas for Improvement

• Complexity Management: The function handleMessage contains nested logic that could be refactored into smaller functions for better readability and maintainability.
• Logging: While there is some logging present, more detailed logging could help in debugging issues related to message handling.

4. src/search/metaSearchAgent.ts

Structure and Quality

• Class Design: The MetaSearchAgent class encapsulates search functionality with methods like createSearchRetrieverChain and createAnsweringChain.
• Configurable Behavior: The use of a configuration object allows for flexible behavior across different search modes.
• Asynchronous Processing: Promises are used effectively to handle asynchronous operations, such as fetching documents and embeddings.

Areas for Improvement

• Complexity Reduction: Some methods within the class are quite lengthy and could be broken down into smaller helper functions to improve readability.
• Error Handling: While there are try-catch blocks present, more granular error handling within asynchronous operations could improve reliability.
• Documentation: Inline documentation explaining the purpose of complex logic or algorithms would aid in understanding the codebase.

Overall, the codebase demonstrates solid engineering practices with room for improvement in modularity, error handling, and documentation. Refactoring complex components into smaller units can enhance maintainability as the project evolves.

Report On: Fetch commits

Development Team and Recent Activity

Team Members and Their Activities

ItzCrazyKns

• Recent Commits: 6 commits in the past 14 days.
• Activities:
  • Merged branches and pull requests.
  • Worked on UI components, particularly ChatWindow.tsx and SearchVideos.tsx.
  • Implemented features such as showing settings during errors on mobile, linting, and beautifying code.
  • Collaborated with other developers by merging their pull requests.
• Files Modified: Primarily worked on UI components with significant changes in ChatWindow.tsx.

realies

• Recent Commits: 1 commit in the past 14 days.
• Activities:
  • Added an exponential reconnect mechanism for websocket errors.
• Files Modified: ChatWindow.tsx.

Sainadh Devireddy

• Recent Commits: 1 commit in the past 14 days.
• Activities:
  • Set page content correctly in metaSearchAgent.ts.

Other Developers

• yassinesmartly, eligrinfeld, sainadh-d, mitchross, asifrahaman13, hacking-racoon, ProjectMoon:
  • No recent commits but have open or closed-unmerged pull requests indicating ongoing or previous collaboration.

Patterns and Themes

• Collaboration: ItzCrazyKns is the primary contributor, frequently merging branches and integrating work from other developers. This suggests a central role in maintaining the project.
• Focus on UI Enhancements: Recent activities heavily focus on improving UI components, particularly the chat window functionality.
• Error Handling Improvements: There is a notable emphasis on improving error handling mechanisms, especially related to websocket connections.
• Code Quality: Regular linting and beautifying of code indicate a focus on maintaining code quality.

Conclusions

The development team is actively working on enhancing user interface components and improving error handling within the Perplexica project. ItzCrazyKns leads these efforts with significant contributions and collaborations with other team members. The project shows signs of active maintenance with regular updates and improvements.