Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Push to Github packages doesn't work

See original GitHub issue

Describe the bug

Dotnet NuGet Push step in the Push GitHub Packages completes with the error.

Run $count = 0;
  $count = 0;
  do {
      ++$count;
      dotnet nuget push .\windows-latest\*.nupkg --source GitHub --skip-duplicate;
  }
  while ($count -lt 30 -and $LastExitCode -ne 0)
  shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'"
  env:
    DOTNET_NOLOGO: true
    DOTNET_SKIP_FIRST_TIME_EXPERIENCE: true
    DOTNET_CLI_TELEMETRY_OPTOUT: true
    MINVERBUILDMETADATA: build.4
warn : No API Key was provided and no API Key could be found for 'https://nuget.pkg.github.com/sharok'. To save an API Key for a source use the 'setApiKey' command.
Pushing testnuget.0.0.0-preview.0.3.nupkg to 'https://nuget.pkg.github.com/sharok'...
  PUT https://nuget.pkg.github.com/sharok/
  NotFound https://nuget.pkg.github.com/sharok/ 192ms
error: Response status code does not indicate success: 404 (Not Found).

To Reproduce

Just created a project to test and didn’t make any changes except in matrix.os to build on windows only.

Expected behaviour

A clear and concise description of what you expected to happen.

Project template

Nuget template. Have no idea how to check the installed version, but it latest. Installed today.

Environment

VS: 2019 SDK: 3.1.401

Issue Analytics

State:
Created 3 years ago
Comments:7 (7 by maintainers)

Top GitHub Comments

1reaction

GeeWeecommented, Sep 30, 2020

I can confirm that before I was unable to publish to github, it now succeeds (still after a bunch of tries though)

1reaction

RehanSaeedcommented, Sep 29, 2020

GitHub have done something to make it much more reliable. It’s still not 100% but fails a lot less. So I say we stick to the current workaround of trying 1000 times to push the package until it gets fixed completely.