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.

Sign up for GitHub

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

Jump to bottom

dependents sometimes returns 0 and causes relevance issues #281

Open
MartinKolarik opened this issue Oct 2, 2018 · 1 comment
Open

dependents sometimes returns 0 and causes relevance issues #281

MartinKolarik opened this issue Oct 2, 2018 · 1 comment
Labels
bug can't fix - npm dependent Issue ultimately caused by wrong data returned by npm API

Comments

@MartinKolarik
Copy link
Collaborator

Affects only some packages (I know about react and lodash) - humanDependents and jsDelivrHits are both zero.
@Haroenv
Copy link
Collaborator

Haroenv commented Oct 3, 2018

humanDependents and dependents is actually broken probably because npm was down during the indexing and then we go back to the fallback value, which is 0. React still seems to have a good relevance because of downloads, so it doesn't seem to be a huge issue for now.

I'd still of course like to see this fixed! :)

@Haroenv Haroenv added the bug label Oct 3, 2018
@Haroenv Haroenv changed the title Some properties have wrong (zero) values dependents sometimes returns 0 and causes relevance issues Jan 23, 2019
@Haroenv Haroenv added the can't fix - npm dependent Issue ultimately caused by wrong data returned by npm API label Jan 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug can't fix - npm dependent Issue ultimately caused by wrong data returned by npm API
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MartinKolarik @Haroenv