Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Symbols folder not found #299

Closed
diegoberges opened this issue Jul 30, 2019 · 3 comments
Closed

Symbols folder not found #299

diegoberges opened this issue Jul 30, 2019 · 3 comments

Comments

@diegoberges
Copy link

Describe the bug

When I try to upload a .snupkg nuget, I recieve an error 404.

To Reproduce

Steps to reproduce the behavior:

  1. Using this version of BaGet 'v0.1.77-prerelease'
  2. Using this version of Nuget '5.0.2.5988'
  3. Run this code 'dotnet nuget push -s http://localhost:5000/v3/index.json Prueba.7.0.11.snupkg '
  4. See error

image

Expected behavior

I think that de files (.nupkg and .snupkg) should upload to server.

Additional context

All Log

$ dotnet nuget push -s http://localhost:5000/v3/index.json Prueba.7.0.11.snupkg 
info : Insertando Prueba.7.0.11.snupkg en 'http://localhost:5000/api/v2/symbol'...
info :   PUT http://localhost:5000/api/v2/symbol/
info :   NotFound http://localhost:5000/api/v2/symbol/ 110 ms 
error: Response status code does not indicate success: 404 (Not Found).
@loic-sharma
Copy link
Owner

Hello, this is expected behavior: you cannot push a NuGet symbols package without first pushing its corresponding NuGet package. I've opened a NuGet issue to improve this error message: NuGet/Home#8404

Please let me know if you have any suggestions in this area! I'll close this off for now, but feel free to reply or open a new issue if needed 😄

@diegoberges
Copy link
Author

Hello, OK, but this is my workflow, first I upload the nuget and after that I upload the symbols.

I think that, firstle, the error code must be more clearer to the user, not an 404 error.

@loic-sharma
Copy link
Owner

Ideally, the protocol is an implementation detail hidden by the NuGet client. The protocol can be unclear so long as the client provides a good experience. Also, the NuGet protocol is hard to change, as we need compatibility with existing NuGet clients.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants