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: Maven 403s #11

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

Triage Crawler exceptions: Maven 403s #11

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

Comments

@brphelps
Copy link
Contributor

exceptions
| summarize
Maven403 = countif(outerMessage contains "StatusCodeError: 403" and outerMessage contains "maven")

@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 13, 2020
@jeffmendoza
Copy link
Member

looking into these: they are valid requests that we are making, the packages/files exist. I believe the 403's are due to us being throttled/blocked by maven for not following their robots policy.

@jeffmendoza
Copy link
Member

Either way, these should just be logged as a crawl error, not exception.

Of course, like others we are only getting this at ghcrawler/lib/crawler.js:132, need to come up with a solution for all these.

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