RocketChat / RocketChat/Rocket.Chat
Trying to disable a connected user doesn't works and cause crash
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
App crashes when trying to disable a connected user.
Steps to reproduce:
- Go to Admin > Users
- Select a connected user
- Click on Action Button (3 dots) > Select "Disable" in the dropdown menu
Expected behavior:
Target user session should be terminated and user should be forcefully disconnected and disabled.
Actual behavior:
App crashes and user is neither disabled nor forcefully disconnected
Server Setup Information:
- Version of Rocket.Chat Server: 4.6.0
- Operating System: Ubuntu 18 LTS
- Deployment Method: Docker Compose
- Number of Running Instances: 1
- DB Replicaset Oplog: Enabled
- NodeJS Version: 14.18.3 - x64
- MongoDB Version : 4.2.17 / wiredTiger (oplog enabled)
Client Setup Information
- Desktop App or Browser Version: 3.8.2
- Operating System: Windows 11 Professional
Relevant logs:
No relevant server or client logs.
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
Reproduce the crash from Admin > Users by selecting a connected user and choosing Disable, then inspect the available client and server logs around that action. Trace the disable flow from the user action through session termination and identify the crash cause. Done means the user is disabled, their session is terminated, and the app remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100