nuts-foundation / nuts-foundation/nuts-node
vcr: name gRPC network transport in publish-failure error message (+ backports)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Tracks the third checklist item from nuts-foundation/nuts-node#4515 (comment): "Test whether a (helpful) message is returned by the IssueVC REST API operation when issuance over both OpenID4VCI and gRPC network fails. It should describe why both methods failed."
Together with #4470 (joins the OpenID4VCI and network-publish errors), #4516 makes the network-publish error explicitly name gRPC as the transport, so the combined error read by an IssueVC caller distinguishes the two failures instead of showing two near-identical messages.
Tasks
- PR to master: #4516
- Backport to v6.2: #4520
- Backport to v5.4: #4521
Assisted by AI
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
Start by reviewing PR #4516 and the backport tasks in #4520 and #4521. Confirm how the network-publish error names gRPC, then complete the v6.2 and v5.4 backports so the combined IssueVC failure distinguishes gRPC from OpenID4VCI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100