Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    ProGet 2023.13: Delay after package upload

    Scheduled Pinned Locked Moved Support
    3 Posts 2 Posters 23 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C Offline
      caterina
      last edited by

      Hi,

      we noticed a delay between uploading a package and being able to do a nuget restore on a consumer of this package.

      More specific:
      We uploaded a new package "DAP.Common 7.0.13" to ProGet. Afterwards, we updated the dependency to this new version manually in a consuming project. We tried to call nuget restore but it failed with the following error: "Unable to find package DAP.Common with version (>= 7.0.13)". There were about 15 minutes between package upload and nuget restore. A few minutes later we tried it again and the package was found. But the package could be seen on ProGet right after the uplaod.
      We were able to observe this behavior with several packages. If the dependency got updated manually in a consuming project, nuget restore failed for a certain time period.

      Unfortunately, we can not say if the problem is still present if the nuget package manager in Visual Studio would have been used to update the package dependency.

      Have you already seen such a behavior?

      1 Reply Last reply Reply Quote 0
      • Dan_WoolfD Offline
        Dan_Woolf inedo-engineer
        last edited by

        Hi @caterina,

        This has been an issue we see from time to time and it is related to NuGet's request caching. One thing to try first is to make sure you do not have IIS request caching enabled. To do this:

        1. Navigate to your ProGet site in IIS
        2. Double click on "Output caching"
        3. On the right, click "Edit Feature Settings..."
        4. Uncheck both "Enable cache" and "Enable Kernel Cache"
        5. Click OK

        The next thing to try is to clear NuGet's HTTP cache. You can do that by running the following NuGet command:

        nuget locals http-cache -clear
        

        Typically the combination of these will resolve the issue. Can you please try these next time you have the issue?

        Thanks,
        Dan

        1 Reply Last reply Reply Quote 0
        • C Offline
          caterina
          last edited by

          Hi @Dan_Woolf,

          so it seems to be a long known issue: https://github.com/NuGet/Home/issues/3116

          Thank you for your help.
          Caterina

          1 Reply Last reply Reply Quote 0

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • 1 / 1
          • First post
            Last post
          Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation