You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Current implementation has an exception when persisting package metadata into an AzureTable
To Reproduce
Steps to reproduce the behavior:
Using this version of BaGet: 'v0.3.0-preview5'
Run this code: docker run --rm --name nuget-server -p 5555:80 --env-file baget.env -v "$(pwd)/baget-data:/var/baget" loicsharma/baget:latest [as per documentaiton]
With these arguments:
environment variables
Database__Type=AzureTable
Database__ConnectionString=DefaultEndpointsProtocol=https;AccountName=XXXXX;AccountKey=XXXXX;TableEndpoint=XXXX
See error
Expected behavior
Package to be uploaded successfully with metadata in AzureTable
Screenshots
Additional context
It would appear that the Id property causes issues with serialization as this is a reserved keyword
Got the hint from this link
I have been able to fix this and will link this issue to a pull request #669
The text was updated successfully, but these errors were encountered:
Describe the bug
The Current implementation has an exception when persisting package metadata into an AzureTable
To Reproduce
Steps to reproduce the behavior:
Using this version of BaGet: 'v0.3.0-preview5'
Run this code: docker run --rm --name nuget-server -p 5555:80 --env-file baget.env -v "$(pwd)/baget-data:/var/baget" loicsharma/baget:latest [as per documentaiton]
With these arguments:
environment variables
Database__Type=AzureTable
Database__ConnectionString=DefaultEndpointsProtocol=https;AccountName=XXXXX;AccountKey=XXXXX;TableEndpoint=XXXX
See error
Expected behavior
Package to be uploaded successfully with metadata in AzureTable
Screenshots
Additional context
It would appear that the Id property causes issues with serialization as this is a reserved keyword
Got the hint from this link
I have been able to fix this and will link this issue to a pull request #669
The text was updated successfully, but these errors were encountered: