RocketChat / RocketChat/Rocket.Chat

Bug with the number of notification counted by the cloudconsole

Open
#20,299 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Hello,

Steps to reproduce : Send one message, getting five counted ;
Expected behavior : Send one message, only one counted
Actual behavior : Cloud Console Show 5 notifications counted
Server Setup Information : Version de Node | v12.18.4, Version de Mongo : 3.6.14, i'm using snap install on ubuntu 20.04 Lts
Version of Rocket.Chat Server : last version 3.9.3

Since Rocketchat decide to monitorize the notification, i'm having issue with the counting of notification.

I've this particular user i'm sending a message in a private discussion and it's counting as 5 notificaiton in the cloud console.

So i thought i will deactivate the user to be sure he is not connected elsewhere and just getting notification throug his phone.

But even though, its counting 5 notifications when only one message is send.

Its a bit problematic....

Any thougt on that ?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the report in the Cloud Console using a private discussion: send one message and verify whether five notifications are counted. Check the reported Node.js, MongoDB, Ubuntu, and Rocket.Chat versions while narrowing down whether the duplicate count comes from the server or notification monitoring. Done means one sent message produces one counted notification.

Written by the indexing model from the issue text.

Assessment

Tech stack
mongodb, node.js
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.