0c60fa9c23
Closes https://github.com/twentyhq/core-team-issues/issues/861 sentries: [User workspace role map not found after recompute](https://twenty-v7.sentry.io/issues/6575092700/events/f9825338a30b470eb2345fe78c1e3479/?project=4507072499810304&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D%20not%20found%20after%20recompute&referrer=next-event&stream_index=0) (64 events in 90d), [Feature flag map not found after recompute](https://twenty-v7.sentry.io/issues/6547696076/?project=4507072499810304&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D%20not%20found%20after%20recompute&referrer=issue-stream&stream_index=1) (23 events in 90d) We have a structural issue with cached data and our locking mechanism: if a data is missing in cache and queried at the same time by two different entities, the first one will recompute the data and indicate a lock during the operation, while the second one will seek to recompute the data too but be stopped because of the ongoing lock, and be left with no data to use, condemned to throw an error. In this PR I considered that it was more important to avoid that error and chose to ignoreLock instead when the data is being queried (through getFromCacheWithRecompute), but this is maybe questionnable. An important note is that I can't figure out how users that regularly use twenty (as it has been the case since this error occured on our internal workspace) can encounter that error as once computed, **the key should always be present in the workspace**: the corresponding value it is always updated, never deleted (until this PR) and recreated. I was not able understand how this happened For our data cached without a version to refer to in the database, I also chose to ignore the lock when the recompute is triggered by a data change (eg feature flag enabling or assigning user to a role or adding an objectPermission on a role, etc.), as we never want to imped the recompute in that case to avoid potential stale data.
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · 
Roadmap · 
Discord · 
Figma
Installation
See:
🚀 Self-hosting
🖥️ Local Setup
Does the world need another CRM?
We built Twenty for three reasons:
CRMs are too expensive, and users are trapped. Companies use locked-in customer data to hike prices. It shouldn't be that way.
A fresh start is required to build a better experience. We can learn from past mistakes and craft a cohesive experience inspired by new UX patterns from tools like Notion, Airtable or Linear.
We believe in Open-source and community. Hundreds of developers are already building Twenty together. Once we have plugin capabilities, a whole ecosystem will grow around it.
What You Can Do With Twenty
We're currently developing Twenty's beta version.
Please feel free to flag any specific needs you have by creating an issue.
Below are a few features we have implemented to date:
- Add, filter, sort, edit, and track customers
- Create one or several opportunities for each company
- See rich notes tasks displayed in a timeline
- Create tasks on records
- Navigate quickly through the app using keyboard shortcuts and search
Add, filter, sort, edit, and track customers:
Create one or several opportunities for each company:
Track deals effortlessly with the email integration:
Tailor your data model to meet business needs:
See rich notes displayed in a timeline:
Create tasks on records
Navigate quickly through the app using keyboard shortcuts and search:
Connect your CRM to all your tools through our APIs and Webhooks.
Stack
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Recoil, Emotion 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
- Subscribe to releases (watch -> custom -> releases)
- Follow us on Twitter or LinkedIn
- Join our Discord
- Improve translations on Crowdin
- Contributions are, of course, most welcome!