search

ava-labs / avalanche-cli

Other
104 stars 66 forks source link

bug: 403 while checking for cli update #2012

Open arturrez opened 4 months ago

arturrez commented 4 months ago 
❯ ./scripts/build.sh &&  ./bin/avalanche node destroy p1 -y ; ./bin/avalanche node create p1 --use-static-ip=false --latest-avalanchego-version=true --aws  --region us-east-1 --num-validators=2  --num-apis=2 --fuji  --node-type=default --enable-monitoring=true
Error: cluster "p1" not found
Error: failed doing request https://api.github.com/repos/ava-labs/avalanchego/releases/latest: unexpected http status code: 403
❯ curl -v https://api.github.com/repos/ava-labs/avalanchego/releases/latest
... 
< HTTP/2 403 
< date: Tue, 02 Jul 2024 17:52:39 GMT
< server: Varnish
...
< 
{"message":"API rate limit exceeded for XX.XX.XX.XX. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://docs.github.com/rest/overview/resources-in-the-rest-api#rate-limiting"}
* Connection #0 to host api.github.com left intact
containerman17 commented 3 months ago

My guess is that the Avalanche CLI checks for updates, fails to do so, and then fails completely. IMHO, it would be better if it just skipped the update if it fails.