Weekly GitHub Report for Monica: October 31, 2024 - November 07, 2024

Weekly GitHub Report for Monica

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. Issues
  • 1.1. Top 5 Active Issues
  • 1.2. Top 5 Stale Issues
  • 1.3. Open Issues
  • 1.4. Closed Issues

• II. Pull Requests
  • 2.1. Open Pull Requests
  • 2.2. Closed Pull Requests
  • 2.3. Pull Request Discussion Insights

• III. Commits
  • 3.1. Commits

• IV. Contributors
  • 4.1. Contributors

I. Issues

1.1 Top 5 Active Issues:

We consider active issues to be issues that that have been commented on most frequently within the last week.

1. [Chandler] Setting QUEUE_CONNECTION to redis causes Chandler not working: This issue reports a bug where setting the QUEUE_CONNECTION to redis results in Chandler not functioning properly, as jobs dispatched to the queues do not execute. The user expects that by resolving this issue, essential features such as modules, currencies, default settings, and email notifications will work as intended.

   • Multiple users confirmed the issue occurs with different database setups, and while some have successfully used Redis without problems, others noted that switching to sync resolves the functionality issues. There is a suggestion that the problem may be related to Laravel rather than Chandler itself, prompting a recommendation to report it to Laravel if necessary.
   • Number of comments this week: 4

2. AI Chatbot support for Q&A and Actions, aka ChatGPT for Monica: This issue proposes the integration of an AI chatbot, similar to ChatGPT, into the Monica application to enhance user interaction by allowing users to ask questions about their contacts and perform tasks through a chat interface. The discussion highlights potential challenges, such as the need for efficient data handling and the implications of using large language models, while also considering alternative approaches like a Chrome extension.

   • The comments reflect a constructive dialogue about the feasibility of integrating AI support, with suggestions on managing data efficiently and exploring different methods to implement the feature. Participants express enthusiasm for the idea while addressing potential challenges related to token usage and data privacy.
   • Number of comments this week: 3

3. Inconsistent password requirements: This issue highlights a bug in the Monica application where the password requirements for admin accounts differ from those for user accounts. Specifically, a password that is accepted for an admin account is rejected for a user account, leading to confusion and inconsistency in user experience.

   • The comments discuss the process of creating an admin account and the differing password acceptance. One user notes that they encountered a similar issue previously, suggesting that the problem may have been addressed in a recent update.
   • Number of comments this week: 3

4. How do I increase storage on Chandler beyond 50MB? [Selfhosted]: This issue revolves around a user seeking guidance on how to increase the storage limit of the Chandler application, which is currently capped at 50MB, while self-hosting it using Docker. The user is looking for a solution to allow for unlimited storage to accommodate larger files, such as profile pictures.

   • The comments reflect a shared concern about storage limits, with one user expressing a similar question. Another comment clarifies that this inquiry is not categorized as an issue but rather belongs in the Discussions section, while a third comment provides a potential workaround involving direct SQL updates to the database for self-hosted setups.
   • Number of comments this week: 3

5. Support "unlimited" storage in Chandler: This issue requests the implementation of "unlimited" storage for users in the Chandler project, suggesting that setting the storage limit to -1 should indicate no limit, while 0 would signify no uploads allowed. The user highlights that the current version does not interpret a limit of 0 as infinite, as it did in a previous version, and seeks a more explicit solution for managing storage limits.

   • The comments discuss the current behavior of the storage limit settings, with one user noting that the documentation suggests 0 means unlimited, while others confirm that version 5 does not honor this setting as version 4 did. There is a consensus that the user interface should be updated to reflect "Unlimited" instead of 0 when no limits are applied.
   • Number of comments this week: 3

1.2 Top 5 Stale Issues:

We consider stale issues to be issues that have been opened in this project for the longest time within the last year. The team should work together to get these issues resolved and closed as soon as possible.

1. AI Chatbot support for Q&A and Actions, aka ChatGPT for Monica: This issue is a feature request for integrating AI chatbot support, specifically similar to ChatGPT, into the Monica application to enhance user interaction with their contacts. The proposed solution includes creating a chat interface that allows users to ask questions about their contacts and perform simple tasks through text commands, addressing the current lack of built-in AI capabilities as noted in the project's README.

   • Open for 356 days, 07 hours, 30 minutes

2. Monica API: occupation and company are not visible: This issue reports a bug in the Monica API where the occupation and company information for contacts are not displayed in the user interface, despite being created through the API. The user expected to see this information on the overview page under work information but found that the relevant API endpoints may not be properly integrated with the application.

   • Open for 353 days, 16 hours, 34 minutes

3. Undefined in post title input as default: This issue pertains to a bug encountered during the creation of posts in the application, where the title input defaults to "undefined" instead of being empty, leading to unintended post submissions even when no title is provided. The user has reported that this behavior occurs in both Regular and Inspirational post creation, causing confusion and frustration as it allows posts to be created without valid titles.

   • Open for 353 days, 08 hours, 46 minutes

4. Inconsistent password requirements: This issue highlights a bug in the Monica application where the password requirements for admin accounts differ from those for user accounts, causing confusion during account creation. Specifically, while an admin account can accept a password containing special characters, such as !, the same password is rejected for user accounts, leading to an inconsistent user experience.

   • Open for 347 days, 19 hours, 41 minutes

5. [Chandler] Setting QUEUE_CONNECTION to redis causes Chandler not working: This issue reports a bug where setting the QUEUE_CONNECTION to redis results in Chandler becoming non-functional, as jobs dispatched to the queues fail to execute. The user highlights that this malfunction leads to missing essential features such as modules, currencies, default settings, and email sending capabilities, rendering the application largely unusable.

   • Open for 347 days, 01 hours, 31 minutes

1.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: 2

Summarized Issues:

• Contact Sync Issues: This topic addresses problems related to the synchronization of contacts in the Monica application. Users have reported that contacts synced via CardDAV are not consistently added, which can lead to them disappearing from audit logs. This issue raises concerns about the potential for silent deletions of contacts without any notification to the user.
  • github.com/...

• Storage Limit Bugs: This topic highlights a bug in the Monica 5.0.0-beta.4-apache version regarding the user's storage limit. The DEFAULT_MAX_STORAGE_SIZE key fails to update, resulting in users being incorrectly limited to 50MB instead of the intended 20,000MB. This discrepancy can lead to confusion and hinder users' ability to manage their data effectively.
  • github.com/...

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

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

Based on our analysis, there are no instances of toxic discussions in the project's open issues from the past week.

---

II. Pull Requests

2.1 Open Pull Requests

This section lists and summarizes pull requests that were created within the last week in the repository.

Pull Requests Opened This Week: 3

Pull Requests:

• API Search Functionality Improvements: This topic covers enhancements made to the API search results, specifically focusing on the accurate representation of the is_active and is_dead boolean values. The modifications ensure that archived contacts are excluded from search results by limiting them to those where is_active is true. This change aims to improve the relevance and accuracy of the data returned by the API.
  • github.com/monicahq/monica/pull/7436

• Contact Relationship Form Updates: This topic addresses the issue of form data not being updated correctly in the contact relationship form when toggling between the "I know the name" and "I don't know the name" options. A new function has been introduced to clear the relevant fields, ensuring that the form submits correctly regardless of the selected option. This improvement enhances the usability of the form for users.
  • github.com/monicahq/monica/pull/7446

• Error Handling for Missing Files: This topic focuses on improving user experience by adding an error message that is displayed when a requested file is not found within the Monica project. This enhancement aims to provide clearer feedback to users, helping them understand when a file is unavailable. By implementing this feature, the project aims to reduce confusion and improve overall user satisfaction.
  • github.com/monicahq/monica/pull/7447

2.2 Closed Pull Requests

This section lists and summarizes pull requests that were closed within the last week in the repository. Similar pull requests are grouped, and associated commits are linked if applicable.

Pull Requests Closed This Week: 0

Summarized Pull Requests:

As of our latest update, there are no closed pull requests for the project this week.

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

1. fix: correct boolean values and exclude archived results from search

   • Toxicity Score: 0.55 (Disagreement on implementation, fluctuating tone, expressions of frustration)
   • This GitHub conversation begins with the author expressing surprise at the presence of archived contacts in search results, while also suggesting a solution to improve the accuracy of boolean values. As the discussion progresses, other contributors weigh in with varying degrees of agreement and skepticism, leading to moments of tension when differing opinions on the proposed changes arise. Some participants express frustration over the perceived rigidity of the suggestions, while others advocate for the necessity of the adjustments. The tone fluctuates between collaborative and confrontational, reflecting the challenges of reaching consensus on the implementation details.

2. fix: update form data on radio button change in contact relationship form (#7226)

   • Toxicity Score: 0.65 (Misunderstandings, escalating emotions, defensive responses)
   • This GitHub conversation begins with username1 presenting a solution to a problem related to form data not updating correctly in a contact relationship form. Username2 acknowledges the solution but raises a concern about its implementation, leading to a back-and-forth exchange. As the discussion progresses, username1 expresses frustration over the lack of clarity in username2's feedback, while username2 defends their position, resulting in a noticeable increase in tension. The tone shifts as both users attempt to clarify their points, but misunderstandings persist, causing further irritation. Ultimately, the conversation reflects a mix of constructive criticism and escalating emotions, highlighting the challenges of effective communication in collaborative environments.

3. Add error mesage to file not found

   • Toxicity Score: 0.67 (Defensive responses, frustration, dismissive comments)
   • This GitHub conversation begins with username1 expressing confusion over an error message related to a file not being found, prompting username2 to provide a potential solution. As the discussion progresses, username1's tone shifts to frustration when username2's suggestion does not resolve the issue, leading to a back-and-forth exchange where username2 becomes defensive. Tension escalates further when username3 joins the conversation, questioning the clarity of the initial problem, which causes username1 to feel dismissed. The overall sentiment fluctuates between helpfulness and irritation, indicating a growing sense of discord among the participants.

---

III. Commits

3.1 Commits

This section lists and summarizes commits made within the last week and groups them based on topic.

Commits Made This Week: 0

Summarized Commits:

As of our latest update, there are no commits for the project this 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.

Contributor	Commits	Pull Requests	Issues	Comments
djaiss	0	6	0	3
Mazarin	6	0	0	0
DanteB918	0	2	0	2
shreyashrpawar	0	3	0	0
Dante Bradshaw	2	0	0	0
Otanga-Otieno	0	1	0	1
Abdalrashid Saeed Soliman	1	0	0	0
phblj	1	0	0	0
Lukas Rosenstock	1	0	0	0
Alexis Saettler	1	0	0	0