The productive version of Microsoft.Testing.Extensions.HangDump must not reference to a preview version of Microsoft.Diagnostics.NETCore.Client
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start with the HangDump extension project's csproj and find the PackageReference to Microsoft.Diagnostics.NETCore.Client pinned at 0.2.607501. Check on NuGet.org whether a stable release is available and compatible, since the issue is about the preview reference. Done means the extension references only stable packages and its build and tests still pass, which the maintainers may need to confirm before merging.
Written by the indexing model from the issue text.
Description
Describe the bug
The package Microsoft.Testing.Extensions.HangDump in version 2.5.1 references to the package Microsoft.Diagnostics.NETCore.Client in version 0.2.607501, which is assemed to be a preview or alpha version.
A productive package like HangDump should reference to productive packages only.
Version used
Microsoft.Testing.Extensions.HangDump 2.5.1
Steps To Reproduce
N/A
Expected behavior
All references of Microsoft.Testing.Extensions.HangDump have the same release state as the package itself.
Actual behavior
Microsoft.Testing.Extensions.HangDump seems to be productive, but refers to a preview version.
Additional context
We have clear strategy to consume packages from NuGet.org. Packages are checked about the current development state. Packages should be consistent and under maintenance.
While Microsoft.Testing.Extensions.HangDump is assumed to be well maintained, the reference to Microsoft.Diagnostics.NETCore.Client 0.2.607501 breaks the chain of trust.
- Dominant language
- C#
- Stars
- 1.1k
- Forks
- 312
- Avg merge
- 8h 33m
- Merged PRs (30d)
- 411
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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/testfx
-
type/automation type/tech-debt
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
needs/triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
type/automation type/tech-debt
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
agentic-workflows type/automation type/tech-debt
Difficulty 1/5 Under an hour Newbie friendliness 1/100
Maintainers usually reply within 1 day
-
area/mtp-github-actions-report external/dotnet-test needs/triage
Difficulty 4/5 3-5 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
All issues in microsoft/testfx
Similar issues
-
bug priority: P2
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
[Docs] README/PRIVACY still name AppCenter although v1.5.6.0+ uses the Microsoft Store Services SDKOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Azure/azure-sdk-tools#17317 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
swisstopo/swissgeol-boreholes-suite#3086 ·
Maintainers usually reply within 1 day