websockets-rs / websockets-rs/rust-websocket
Some data frame opcodes not being handled at all
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 225
- PR merge metrics
- No merged PRs in 30d
Description
To be specific, serenity (the crate i'm the current maintainer of) has sometimes after a while when booting up, lots of spam regarding unknown/invalid data frame opcodes.
But the thing is, the other api wrappers for discord are working just fine without anything interrupting them with data frame opcodes.
So by my assumption, there has to be some opcodes not being handled by this crate at all.
Contributor guide
No contributing guide indexed for this repository
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 file or test is named. Start by tracing how the crate parses and dispatches data-frame opcodes, then reproduce the unknown/invalid opcode messages described with Serenity; done means identifying which valid opcodes are mishandled and covering the behavior with an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100