Distinguish between `key_ops` being omitted and key_ops: [] in jwk
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c, javascript, wasm
- Domain
- backend
Research direction
Read the linked discussion in pull request #330, which is the only pointer in this issue, and trace how JWK key_ops is parsed and represented in StarlingMonkey. Determine where omission and an empty array need distinct handling, then add or update coverage for both cases. Done means the two inputs are distinguishable and the relevant tests pass.
Written by the indexing model from the issue text.
Description
- Dominant language
- C
- Stars
- 295
- Forks
- 62
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 15
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from bytecodealliance/StarlingMonkey
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bytecodealliance/StarlingMonkey#343 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
bytecodealliance/StarlingMonkey#345 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
bytecodealliance/StarlingMonkey#344 · 1 comment ·
Maintainers usually reply within 2 days
-
The forgiving decoder implementation is ignoring padding and whitespaces in crypto-algorithm.cppOpen
Difficulty 2/5 1-3 hours Newbie friendliness 52/100
bytecodealliance/StarlingMonkey#338 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
bytecodealliance/StarlingMonkey#322 · 2 comments · 1 reaction ·
Maintainers usually reply within 2 days
All issues in bytecodealliance/StarlingMonkey
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
area:buffer good first issue type:documentation
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sudo-project/sudo#586 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
Abort (SIGABRT) when stderr is a closed pipe: uncaught fmt::system_error in ccache_main's catchPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days