RocketChat / RocketChat/Rocket.Chat
Repeated message "You have [n] seats left."
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Since upgrading to Rocket.Chat 6.4.5 from 5.x, administrators get a warning "You have [n] seats left." displayed. The message reappears 1-2 hours after dismissing it and continues coming back. Previously, this message would only occur when Rocket.Chat was updated or when the number of users on the instance changed.
After dismissing the message, an error message message "Invalid Params" would briefly appear as well.
The server synchronizes the user database from LDAP, but this sync occurs every 24 hours. The seats message is displayed more frequently than that.
This seems similar to #23457 although I did not experience this prior to the upgrade to version 6.
Expected behavior:
When I acknowledge the "You have [n] seats left." message, it does not reappear unless the number of seats changes.
Actual behavior:
The message reappears frequently. Perhaps every 1-2 hours after dismissing the previous one.
Server Setup Information:
- Version of Rocket.Chat Server: 6.4.5
- Operating System: Ubuntu GNU/Linux 20.04.6
- Deployment Method: Snap
- Number of Running Instances: 1
- NodeJS Version: v14.21.2
- MongoDB Version: 5.0.15 / wiredTiger (oplog Enabled)
Client Setup Information
- Desktop App or Browser Version: Occurs with Client and FireFox Browser
- Operating System: Windows and Linux
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reproducing the repeated seat warning on Rocket.Chat 6.4.5 with the described LDAP synchronization setup, then trace the warning dismissal and seat-change handling. Done means the warning stays dismissed until the seat count changes and the accompanying "Invalid Params" message no longer appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, node.js, typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100