RFC 0379: gRPC API: Update netlaunch to use RCP
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
The issue body is empty, so begin by locating the netlaunch entry point and the existing gRPC API integration in the repository. Read RFC 0379 and inspect how netlaunch currently communicates before determining the scope of the RCP change. Done means netlaunch uses RCP as specified by the RFC, with the relevant tests updated.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Rust
- Stars
- 32
- Forks
- 18
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 31
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.
More from microsoft/trident
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
All issues in microsoft/trident
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100