You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you're running sctl in a lot of loops you can trigger the github ratelimit for unauthenticated API:
INFO[0002] failed to check for latest version: GET https://api.github.com/repos/vapor-ware/sctl/tags: 403 API rate limit exceeded for 108.56.192.95. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.) [rate reset in 30m13s]
I don't think this is a bad thing, but I do think the logging should be lowered so it's not included in default output.
The text was updated successfully, but these errors were encountered:
ah, this is on the update check 🤔 good point. we didn't want to just swallow that output when we initially landed it 🤔 we may need a better qualifier for when to surface a failed update check.
Currently if you're running sctl in a lot of loops you can trigger the github ratelimit for unauthenticated API:
I don't think this is a bad thing, but I do think the logging should be lowered so it's not included in default output.
The text was updated successfully, but these errors were encountered: