🚸 Auto refresh cloud-hosted instance entry after start/stop until instance is Deployed/Stopped
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the cloud-hosted instance entry and the code handling start and stop status updates. Trace how status changes are refreshed, then verify that background updates continue until the instance reaches Deployed or Stopped.
Written by the indexing model from the issue text.
Description
It would be nice if, after starting or stopping a cloud-hosted instance, the entry for that instance would get refreshed continuously in the background until the status is changed to Deployed/Stopped.
- Dominant language
- C#
- Stars
- 122
- Forks
- 58
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 2
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 microsoft/2LCS
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
bug
Difficulty 2/5 Half a day Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Type:Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
NuGet/NuGetGallery#11026 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
PCL-Community/PCL-CE#3652 ·
Maintainers usually reply within 1 day
-
agentic-workflows Needs: Triage :mag:
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
MCP error results with only structuredContent lose their payloadPossibly taken @sylvesterkaczmarek claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
anthropics/anthropic-sdk-csharp#286 ·
Maintainers usually reply within 1 day