fsprojects / fsprojects/Paket

Unable to find package spontaneous error

Open
#2,916 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug extern sdk: dotnet/sdk
Dominant language
F#
Stars
2.1k
Forks
528
Avg merge
1d 12m
Merged PRs (30d)
54

Description

Description

.Net Core 2

We're using the Nexus OSS repository to provider our internal packages using paket. When we're publishing a new package version and after that execute paket update the packet updates the package to the correct version (it properly see the newest version).
When we open the project in Visual Studio the package (library) is marked with an yellow triangle and the following error occurs in the console:

Error NU1102: Unable to find package X with version (>= 3.1.0.5989790)

  • Found 224 version(s) in Y1 [ Nearest version: 3.1.0.5935616 ]
  • Found 0 version(s) in Y2
  • Found 0 version(s) in Y3

I was trying the "paket clear-cache" and/or delete obj folder and it sometimes helps, but sometimes not :/

Repro steps
  1. Create a package with a version 1.0

  2. Install it in the project with paket.exe install

  3. Create a package with a version 1.1

  4. Update a package

The problem doesn't arise always :/

Expected behavior

Package can bee seen in the Visual Studio project

Actual behavior

Sometimes a package cannot bee seen by the Visual Studio

Known workarounds
nuget locals http-cache -clear
dotnet restore ...

Best Regards,
MiloszeS

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the intermittent failure using paket.exe install, package update, and the two-version package steps described in the issue. Compare the behavior after deleting obj, running paket clear-cache, and running nuget locals http-cache -clear with dotnet restore. Done means the updated package is consistently visible in Visual Studio without the NU1102 error.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.