RocketChat / RocketChat/Rocket.Chat
False alarm: Notifications about an older Rocket.Chat server version(3.5.4) even while being on the latest(3.6.1)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
On opening the desktop app(server and client details below), we are getting this notification even though we are on the latest versions of both the Rocket.Chat server and desktop client.
Steps to reproduce:
- Open the desktop app.
- The false notification pops up as shown in screenshot below.
Expected behavior:
There shouldn't be any such notification if running on the latest version of the Rocket.Chat server instance.
Actual behavior:
Server Setup Information:
- Version of Rocket.Chat Server: 3.6.1
- Operating System: Ubuntu Server 20.04
- Deployment Method: Docker
- Number of Running Instances: 1
- DB Replicaset Oplog: Enabled
- NodeJS Version: v12.16.1 - x64
- MongoDB Version: 4.0.18
Client Setup Information
- Desktop App: 2.17.11
- Operating System: Ubuntu 20.04
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
The payload names no source file or test. Reproduce by opening the desktop app against the listed Rocket.Chat server and client versions, then trace the version-notification entry point and the version data it receives. Done means a current server version no longer triggers the outdated-version warning, with a regression check for this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, mongodb, node.js, typescript
- Domain
- backend, desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100