Investigate empty awareness messages
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
We are seeing some empty awareness messages being send to the clients which led to errors in the browser. We are now filtering them out on the server - but they should not exist in the first place.
I don't know if these are expected off the top of my head. I think we still store the awareness messages in the session data. That might cause an empty string if no awareness has ever been send from the users but the session still exists.
Would be good to clean up the awareness handling.
Originally posted by @max-nextcloud in https://github.com/nextcloud/text/issues/6937#issuecomment-2726322710
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
Start by tracing the server-side awareness handling, including where awareness messages are stored in session data and where empty messages are filtered before reaching clients. Determine whether an empty message is expected or caused by sessions with no awareness data. Done means the cause is established and awareness handling no longer sends invalid empty messages, with the browser error no longer occurring.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100