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

Triage Crawler exceptions: NPM 404s during fetch #16

Open
brphelps opened this issue Mar 12, 2020 · 2 comments
Open

Triage Crawler exceptions: NPM 404s during fetch #16

brphelps opened this issue Mar 12, 2020 · 2 comments
Assignees

Comments

@brphelps
Copy link
Contributor

exceptions | summarize Npm404 = countif(outerMessage contains "404 Not Found" and outerMessage contains "npmjsFetch")

@brphelps
Copy link
Contributor Author

When triaging, make sure to identify whether this issue should or shouldn't be happening -- if it's not truly exceptional, try to convert to a less interesting tracing method (e.g. a warning trace).

@jeffmendoza jeffmendoza self-assigned this Mar 12, 2020
@jeffmendoza
Copy link
Member

Getting a 404 here: https://github.com/clearlydefined/crawler/blob/master/providers/fetch/npmjsFetch.js#L43

should log and move on, not exception. Based on invalid harvest/package/crawl
Interestingly, we see that in the stacktrace, but then it bubbles up to https://github.com/clearlydefined/crawler/blob/master/ghcrawler/lib/crawler.js#L132 where we see a lot of exceptions come from

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