by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jul 07 21:41
    codecov[bot] commented #109
  • Jul 07 21:41
    codecov[bot] commented #109
  • Jul 07 21:36
    dependabot[bot] labeled #109
  • Jul 07 21:36
    dependabot[bot] labeled #109
  • Jul 07 21:36
    dependabot[bot] review_requested #109
  • Jul 07 21:36
    dependabot[bot] opened #109
  • Jul 07 21:36
    dependabot[bot] review_requested #109
  • Jul 07 21:36

    dependabot[bot] on npm_and_yarn

    Bump npm-registry-fetch from 4.… (compare)

  • Jun 15 14:43

    bruno-garcia on master

    (compare)

  • Jun 15 14:43
    bruno-garcia closed #99
  • Jun 15 14:43
    bruno-garcia commented #99
  • Jun 15 14:43

    dependabot[bot] on npm_and_yarn

    (compare)

  • Jun 15 14:43

    dependabot[bot] on npm_and_yarn

    (compare)

  • Jun 15 14:43
    dependabot[bot] commented #95
  • Jun 15 14:43
    joaopgrassi closed #95
  • Jun 15 14:42
    dependabot[bot] commented #108
  • Jun 15 14:42
    joaopgrassi closed #108
  • Jun 15 14:42
    bruno-garcia edited #99
  • Jun 14 20:58
    dependabot[bot] edited #95
  • Jun 14 20:58
    dependabot[bot] edited #108
Bruno Garcia
@bruno-garcia
If you have cool ideas that would make sense on NuGet.org you should consider pitching an idea on NuGetGallery and we could talk it through.
I’ll think about it. Perhaps some of the stuff that came up for nugettrends could be valueable more broadly and we could discuss and I could contribute
thankss
Joel Verhagen
@joelverhagen
Yup, keep up the good work! Feel free to hit us up on Twitter whenever. It seems we have a shared passion, eh?
Bruno Garcia
@bruno-garcia
yeah that’s awesome. Will do. Thanks @joelverhagen
Martin Björkström
@mholo65
Hi @joelverhagen!
Joel Verhagen
@joelverhagen
Hey @mholo65 😀. Too bad we didn't see each other for MVP this year
It was not quite the same as past years 😪
Martin Björkström
@mholo65
Yeah, you weren't even attending the NuGet talk on thursday.
Joel Verhagen
@joelverhagen
Oh c'mon!!! I was at the evening one. But yeah I somehow missed the morning one
Martin Björkström
@mholo65
I gues summit was "ok"... They did the best of the situation, unfortunately timezone is a problem
If you have cool ideas that would make sense on NuGet.org you should consider pitching an idea on NuGetGallery and we could talk it through.
Give us full access to the Gallery data, then we can build stuff 😀
About download counts, could we use the JSON file instead of hitting search endpoint?
Or may we 😀
Joel Verhagen
@joelverhagen
I am so triggered right now haha. I've open that GitHub issue and bring it up with the team every six months or so.
And for opening up gallery data, make a proposal! remember my team has to work within Microsoft accessibility security privacy and availability standards etc
I think the one missing piece for opening up the downloads file in my mind is figuring out how to remove deleted package IDs. There's also some package IDs in that data file that never existed due to a bug and may contain internal package IDs. But honestly in my mind it's pretty close to just opening up. I would need to get my leadership on board though
Bruno Garcia
@bruno-garcia

About download counts, could we use the JSON file instead of hitting search endpoint?

This ^

Joel Verhagen
@joelverhagen
I mean we gotta hit our search query volume goals somehow 😂.
Bruno Garcia
@bruno-garcia
Haha, I got 2 instances of nuget trends running to help u out. there u have ~300k requests per day
Loïc Sharma
@loic-sharma
I believe that Andrei, one of the head honcho engineers on our team, is supposed to work on rebuilding our stats pipeline soon-ish (he’s finishing up a rather big project now, then security compliance stuffs, but then...!)
I’d love to see more public statistic APIs come out of that work
Martin Björkström
@mholo65
@loic-sharma @joelverhagen regarding reverse dependencies and optimizing for querying. Since dependencies are expressed as version ranges, should one a) create a row for each possible version in the range that matches or b) just create one row for the lower bound of the version range. NuGet resolves with the lowest dependency by default, and this is also how NuGet gallery works when clicking a dependency.
Martin Björkström
@mholo65
I know I could just create a bunch of JSON documents and have e.g. Azure Search create the index for me, but trying a different approach with just a bunch of flat tables
Joel Verhagen
@joelverhagen
I think that depends on the desires user experience. In my opinion it's pretty costly and not very useful to have a list of all versions in that range. Depending on the graph or typical project some of these versions may never be selected in practice... Plus this list will grow over time approaching the list of all versions since most people put just the min bound in their dependency version range.
For a UI that shows reverse dependencies, it might just be enough to have [parent id, version] -> [dependency id] as the edge you derive from a nuspec/catalog leaf and build specific documents from that. How useful really is TFM and version range for UI purposes. Needs thought.
@mholo65 ^ since I don't know how notifications work here
Joel Verhagen
@joelverhagen
I guess the thing I'm getting at is why I build a completely thorough document or data structure if there's no scenario around it. Maybe you're thinking of a scenario that I'm not though :-)
The simplest data structure is [parent id] -> [dependency id] but as we know packages pick up and drop dependencies over time so that one's too simple and loses a lot of value. I'm thinking just one step more complex than that.
Like maybe only track the information for the latest version of a package. Hm... Still thinking
I'd just like to keep it as simple as possible for the initial implementation
Martin Björkström
@mholo65
Yeah, as s package maintainer, I'm interested in two three things: 1) Who uses my package, 2) what version are they using and 3) what framework are they targeting.
TFM is good to know as lot's of maintainers are looking into dropping net45 etc and just do ns2.0... Som might even want to go ns2.1 or netcoreapp3.1 in order to use some features... Multi-targeting comes with a cost, if possible people want to drop it..
Version doesn't really matter, all I want to know is if they are using latest or not.
Martin Björkström
@mholo65
To answer my own question, like you also said, edge should be [package id + package version] -> [dependant id + dependant version]... Maybe also group the dependants by TFM..
Joel Verhagen
@joelverhagen
I see, so reverse dependencies TFM is a proxy for TFM adoption. I say proxy because the real indicator is how it's being consumed in shipping products not necessarily libraries. Other library authors are likely operating on the same information as you ( which is very little information... Nuget.org doesn't give any help so far...).
Er, maybe not "shipping products" but volume of package consumers TFM
Martin Björkström
@mholo65
Yes, that's another problems and IIRC, this is even in the NuGet client telemetry. So you don't even know the TFM used for pacakagr restore?
Joel Verhagen
@joelverhagen
I think it's in some VS telemetry, not sure. But definitely not from nuget.exe and probably not from msbuild or .NET cli. It's a partial picture at best ☹️. And for this particular problem just having VS telemetry might give a very skewed picture of TFM adoption
E.g. My bet is .Net framework a
Usage is higher individual studio than in the overall population
Dang voice to text, *in visual studio
Martin Björkström
@mholo65
Yes, VS and .NET CLI definitely have telemetry about TFM usage, but as you said, they probably don't know the packages they reference 😥
Joel Verhagen
@joelverhagen
Hey folks, just wanted to give an update on the reverse dependencies feature on nugat.org. our spring intern is currently neck deep in the implementation but the initial MVP release will just be a gallery experience showing the top N reverse dependencies.
Being able to see the whole list and an API endpoint are stretch goals that may or may not happen in the near term.
Just wanted to give a heads up since we had spoken about it in the past. The PM on our team will be announcing the feature to the community so your thoughts and ideas on the design he proposes would be much appreciated!
Joel Verhagen
@joelverhagen
I think he'll be putting details on Twitter (retweet by nuget no doubt) and NuGet/Announcements. Keep and eye there I think.
Bruno Garcia
@bruno-garcia
@joelverhagen thanks a lot for letting us know. Looking forward to this feature