Sonarly Claude Code
15ccc1ce8d
https://sonarly.com/issue/35824?type=bug Message channel cleanup jobs fail when the repository is created outside the transaction scope, causing connection reuse issues when BullMQ jobs run long enough to lose their lock. Fix: Changed the transaction handling in `MessagingMessageCleanerService` and `CalendarEventCleanerService` to use explicit query runner pattern with proper lifecycle management. **Before:** The code used `workspaceDataSource.transaction()` but created repositories BEFORE the transaction started. When BullMQ jobs ran long enough to lose their lock, connections could be returned to the pool in a corrupted state, causing subsequent `START TRANSACTION` calls to fail with "current transaction is aborted". **After:** Using the explicit pattern: 1. `createQueryRunner()` - creates a dedicated query runner 2. `queryRunner.connect()` - acquires a connection from the pool 3. `queryRunner.startTransaction()` - starts the transaction on that connection 4. `try/catch/finally` with `commitTransaction()`, `rollbackTransaction()`, and `release()` 5. Repository creation happens INSIDE the try block to ensure consistent connection context This pattern ensures: - Proper cleanup even on error (connection always released back to pool) - Transaction is explicitly rolled back on error before releasing - Connection state is guaranteed clean when returned to pool The same fix was applied to both: - `messaging-message-cleaner.service.ts` (deleteMessageChannelMessageAssociationsByChannelId, cleanOrphanMessagesAndThreads) - `calendar-event-cleaner.service.ts` (deleteCalendarChannelEventAssociationsByChannelId)
The #1 Open-Source CRM
Website · 
Documentation · 
Roadmap · 
Discord · 
Figma
Why Twenty
Twenty gives technical teams the building blocks for a custom CRM that meets complex business needs and quickly adapts as the business evolves. Twenty is the CRM you build, ship, and version like the rest of your stack.
Learn more about why we built Twenty
Installation
Cloud
The fastest way to get started. Sign up at twenty.com and spin up a workspace in under a minute, with no infrastructure to manage and always up to date.
Build an app
Scaffold a new app with the Twenty CLI:
npx create-twenty-app my-app
Define objects, fields, and views as code:
import { defineObject, FieldType } from 'twenty-sdk/define';
export default defineObject({
nameSingular: 'deal',
namePlural: 'deals',
labelSingular: 'Deal',
labelPlural: 'Deals',
fields: [
{ name: 'name', label: 'Name', type: FieldType.TEXT },
{ name: 'amount', label: 'Amount', type: FieldType.CURRENCY },
{ name: 'closeDate', label: 'Close Date', type: FieldType.DATE_TIME },
],
});
Then ship it to your workspace:
npx twenty deploy
See the app development guide for objects, views, agents, and logic functions.
Self-hosting
Run Twenty on your own infrastructure with Docker Compose, or contribute locally via the local setup guide.
Everything you need
Twenty gives you the building blocks of a modern CRM (objects, views, workflows, and agents) and lets you extend them as code. Here's a tour of what's in the box.
Want to go deeper? Read the 
User Guide for product walkthroughs, or the Documentation for developer reference.
|
|
|
|
|
|
Learn more about version control in docStack
TypeScript
Nx
NestJS, with BullMQ, 
PostgreSQL, 
Redis
React, with Jotai, Linaria and Lingui
Thanks
Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
Star the repo · Discord · 
Feature requests · Releases · 
X · 
LinkedIn · 
Crowdin · 
Contribute