-
-
Notifications
You must be signed in to change notification settings - Fork 4
Add proper error handling #6
Comments
💜 Happy to help. On https://github.com/exercism/blazon/blob/master/main.go#L146, errors are logged as fatal. Do you see any logged errors around Since rate limiting is per hour, I don't think retries are a good user experience for a cli tool. Maybe the behaviour should just be to clearly report progress and then abort when the script runs into the rate limit, with a message listing what language tracks remain. Problem then is the retry. Can tracks be supplied as arguments, instead of fetched from |
I didn't get any errors at all when I ran it.
It seems odd that we would have used up an hours worth of calls in a single run of the script. Maybe it wasn't that.
I think that would be pretty straight-forward to add, actually.
Yes, that would be really handy. |
It could very well be the rate limit if the calls are unauthenticated. From https://developer.github.com/v3/#rate-limiting
I see an Authorization header, but no authentication. Not sure how I'd add basic auth safely without having the tool ask for username and password every time. But it's something to explore. |
I authenticate using an env var (I use the token authentication). |
Last week we started working on moving track icons into each of the track-specific repositories. See exercism/exercism#2925
I submitted an issue to each track using blazon... and it stopped after submitting to the
r
track. I'm pretty sure that we got rate-limited by GitHub, and that I don't have error handling in the tool to deal with it.Thanks to @martinsvalin who not only discovered this, but also submitted the issue to each of the remaining tracks! ❤️
The text was updated successfully, but these errors were encountered: