playframework / playframework/play-socket.io
No log output when message cannot be parsed
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 96
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
When sending a message which cannot be decoded, like because of a typo in the Json message, the message fails to be processed without any error message in the log.
I was expecting some error.
After fixing the typo, my application worked as expected.
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 reproducing the issue with a malformed JSON message and tracing the message-decoding path. The work is done when the failed decode produces an error in the application log while valid messages continue to be processed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100