Inconsistent behaviour of "paket outdated" depending on selected group
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Running paket outdated -g Main for the main dependency group returns No outdated packages found.
Running paket outdated returns some updates for the same dependency group (which is correct):
Outdated packages found:
Group: Main
* FSharp.Core 5.0 -> 5.0.1
* Microsoft.NETCore.Platforms 5.0 -> 5.0.2
Using paket version 6.0.0-rc002.
Repro steps
See this version of the affected repo:
https://github.com/markpattison/cubes/tree/af6ba5dacce5110a702764984d1ad4ea3df7b266
Expected behavior
Consistent results for paket outdated -g Main and paket outdated.
Actual behavior
Results are inconsistent
Known workarounds
Just run paket outdated, but this is a lot slower (>2 minutes against 12 seconds).
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 reproducing both paket outdated -g Main and paket outdated against the linked cubes repository revision. Compare the selected-group and all-groups execution paths; done means both commands report the same Main-group updates while the scoped command retains its faster runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100