Joined 15 years ago
https://github.com/NuGet/NuGetGallery/issues/9396
Our CDN provider ended up having a shedding mode in some hot areas that made the chain exceed the limit from time to time. Our multi CDN set up saved us so we could do geo specific failovers.
https://github.com/NuGet/Home/issues/new
If you have some ideas in the space of how specifically it could work, maybe mention where/how (e.g. what file) you'd like to declare these "rules".
I've tracked a feature request on GitHub here attempting to represent what was suggested here:
https://github.com/NuGet/NuGetGallery/issues/7824
Add additional comments if you have thoughts on how it should work or anything else. Our backlog is pretty full right now but we'll update this GitHub issue if there is movement.
We have a public unified log (JSON blobs, behind a CDN) containing all events about package publishes, edits, and deletes. The rest of our endpoints have background jobs reading this log and updating different "views" of the package data. Each event's unique ID is a timestamp of when it was added to the log, much like Redis Streams.
We have found this is a powerful concept which has helped us build a very reliable infrastructure where almost all public endpoints are static JSON blobs served by a CDN. The only compute we need for customer API calls is a search service.
We hope one day that our unified log (called the "catalog") will be used for custom client needs and for package replication (e.g. corporations behind a firewall that can't talk to NuGet.org directly).
API docs: https://docs.microsoft.com/en-us/nuget/api/catalog-resource Catalog root: https://api.nuget.org/v3/catalog0/index.json
How does the accuracy (as well as address parsing capabilities) compare to the completely free solutions such as Nominatim[1] or DSTK[2]?
Both services provide capabilities for local installations, obviously with no query limits and minimal latency.
Although it seems it is not working well on Windows 8 x64, I am having a good experience on Windows 7 x64.
A couple of suggestions:
- Wish takes a while to become responsive after starting the program (3-4 seconds for me). I am not sure if this is just me, I just wanted to make you aware!
- Add a keystroke for clearing the terminal. I am addicted to Ctrl + L in bash.
- Perhaps consider adding select to copy.
Keep up the good work, and I'll keep an eye on this project :).
For example, the page on Anime:
Have you found you need to take an aggregate of the two?
How does the quality and completeness of each database compare?
