RocketChat / RocketChat/Rocket.Chat
Messages displaying stops working (Coincidentally when a release is released)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Coincidentally every time a new release is released my rocket chat instance stops showing sent messages, so I send the message, it keeps in a "pending" state, then I reload the view, and the message is there, sent. But all the other users need to also reload the view to see the messages coming.
So when I check, there's a new release out there I just update my K8S deployment with the new image version, and it starts working back again with no issues until the next release.
Steps to reproduce:
- Send a message
- See the message in a pending state
- Reload view
- See the message
Expected behavior:
Send and see the messages right away.
Actual behavior:
I send the message, it keeps in a "pending" state, then I reload the view, and the message is there, sent. But all the other users need to also reload the view to see the messages coming.
Server Setup Information:
- Version of Rocket.Chat Server: 3.17.1 (but it happens in all versions)
- Operating System: Linux
- Deployment Method: docker/k8s
- Number of Running Instances: 1
- DB Replicaset Oplog: Yes
- NodeJS Version: v12.22.1
- MongoDB Version: 4.0.12 / unknown (oplog Ativado)
Client Setup Information
- Desktop App or Browser Version: Desktop App
- Operating System: OSX
Additional context
Relevant 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
No source file, test, entry point, or logs are named in the issue. Reproduce the pending-message behavior around a release and compare the affected deployment with a working one; done means sent messages appear for all users without requiring a view reload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes, mongodb, node.js, typescript
- Domain
- backend, databases, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100