3 posts tagged with "patch notes"

We're excited to share several important updates for the DeviantCord community today!

📣 Now Open Source! We're thrilled to announce that DeviantCord's ecosystem is now publicly available on GitHub! You can now access the repositories for:

• DeviantCord (main application)
• DeviantDBS (database system)
• Documentation website

Feel free to explore our codebase, contribute, and help us improve these projects!

🔄 V4.0.9 Release Our latest beta update focuses on internal improvements, specifically a major code restructuring to enhance maintainability and readability. The main class file has been reorganized, with various functionalities now properly distributed across dedicated files.

🛠️ Technical Updates

• Major code refactoring for improved maintainability
• Resolution of the persistent TransientSQLConnection bug
• Public Root Cause Analysis (RCA) published today detailing the recent connection issues

⚠️ Temporary Internal Code Freeze As of today, DeviantCord will be entering an internal code freeze period until the New Year. During this time:

• Only critical bugs will be addressed by the core team
• No new features will be implemented by the core team
• Regular core development will resume in January 2025

This temporary pause is necessary as our primary developer, Michael, needs to focus on final exams and college commitments.

💡 Community Contributions Welcome! While our core team is on a code freeze, we enthusiastically welcome external contributions! Feel free to:

• Submit pull requests
• Propose new features
• Help improve documentation
• Fix non-critical bugs

🐛 Bug Reporting During Freeze Please continue to report any issues through:

• GitHub Issues on our newly public repositories
• The #beta-bug-reports channel on DeviantCord Discord

📅 Beta Testing Extension Due to the recent technical challenges, we're extending the beta testing period by a few weeks to ensure thorough testing and stability.

Thank you for your understanding and continued support of DeviantCord. We're especially excited to see how the community will engage with our newly open-sourced codebase!

Best regards, The DeviantCord Team

Dear DeviantCord Users,

We want to provide you with an update regarding persistent service challenges and our recent maintenance efforts.

Ongoing Database Connection Issues​

Over the past few weeks, we've been grappling with persistent TransientConnectionSQL Exceptions in our system. This has been particularly challenging to troubleshoot as each potential solution requires 7-8 hours of observation to verify its effectiveness. We've been methodically testing different approaches, but the intermittent nature of these exceptions has made finding a definitive solution time-consuming.

Recent Maintenance​

On November 23rd at 2AM CST, we completed maintenance on our primary dedicated server to apply the latest updates and patches. During this process, we had to temporarily disable DeviantCord services as we continue to address the TransientConnectionSQL Exceptions.

Current Troubleshooting Status​

In our latest attempt to resolve these database connection issues, we have:

• Reduced our node cluster to a single active node
• Temporarily disabled replication on our production PostgreSQL service

DeviantArt API Access Issues & Service Adjustments​

We're currently experiencing widespread access restrictions to DeviantArt's API, with their CloudFront service blocking requests from approximately two-thirds of our servers. In response, we've relocated the bot program and DBS components to servers that still maintain API access. Currently, only one-third of our infrastructure can successfully communicate with DeviantArt's API. We believe this is a temporary issue and are monitoring the situation closely.

Infrastructure Note​

While the affected servers maintain network redundancy, they currently operate without full power redundancy, relying on limited UPS systems. We are aware of this limitation and are managing it accordingly.

Important Bug Fix: AllFolders Feature​

We have resolved a critical bug affecting the AllFolders feature where listeners were not being properly added to the database. Action Required: If you previously set up an allfolder, please verify its presence using the deletefolder command, which will display all active listeners on your server.

Moving Forward​

We understand these ongoing issues may be frustrating, and we appreciate your patience as we work through each potential solution. Our methodical approach, while time-consuming, is necessary to ensure we implement effective, long-term fixes. We anticipate these latest changes will contribute to improved service stability throughout the holiday season.

Our team continues to monitor both the database connection issues and API access situation. We will provide additional updates as we have more information to share.

Thank you for your continued understanding and support.

Best regards,
The DeviantCord Team

We're excited to announce the latest beta release of DeviantCord (v4.0.4), featuring significant performance improvements and bug fixes. This update focuses on enhancing connection handling, improving thread management, and resolving several critical issues with our checking systems.

Important Notice to First-Time Users 📢​

We acknowledge that previous connection and thread management issues prevented many first-time users from successfully testing the bot. If you experienced setup failures or connection timeouts during your initial testing, we strongly encourage you to try again with this new release. The v4.0.4 update specifically addresses these initialization problems and should provide a much smoother onboarding experience.

Performance Improvements 🚀​

Enhanced Database Connection Management​

• Implemented HikariCP optimizations to resolve SQLTransientConnectionExceptions
• Fixed issues where Postgres connections were becoming unavailable

Thread Management Enhancements​

• Implemented stricter CommandExecutors for Slash Command Interactions
• Prevented potential main thread blocking issues
• Migrated da_token Runnable task to a dedicated Executor
• Introduced ThreadFactories for improved thread management

Bug Fixes 🐛​

Check System Improvements​

L1 Check System​

• Resolved hanging issues when retrieving failure reasons
• Fixed Sentry reporting integration

L2 Check System​

• Fixed failure reason retrieval issues
• Restored proper Sentry issue reporting functionality

Folder Management​

• Fixed null pointer exception in AllFolders functionality
• Resolved missing data in responseIds:
  • Added missing artist information
  • Added missing channel information

---

Found a bug or have feedback? Please report it through our Discord support channel.