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
When running lando update, the @lando/cli package fails with message: API rate limit exceeded for [MY.IP.ADDR]. (But here's the good news: Authenticated requests get a higher rate limit
This problem is persistent. I can wait for a hour, day, indeed several weeks and I always get this message.
All other packages can be updated successfully.
Aa a workaround: If I connect to a VPN (and hence change my IP) the problem goes away and I am able to update @lando/cli.
I've tried removing caches in ~/.lando/cache.
I've tried setting up an auth.json file to authenticate my github requests - but confess I'm not entirely sure where I need to place the auth.json file.
The problem occurs in the v3.23.1 version of lando and several versions prior to that. I generally keep lando up to date and it has been occurring for about a month.
My OS is Ubuntu 22.04 running through WSL2.
The text was updated successfully, but these errors were encountered:
When running
lando update
, the@lando/cli
package fails with message:API rate limit exceeded for [MY.IP.ADDR]. (But here's the good news: Authenticated requests get a higher rate limit
This problem is persistent. I can wait for a hour, day, indeed several weeks and I always get this message.
All other packages can be updated successfully.
Aa a workaround: If I connect to a VPN (and hence change my IP) the problem goes away and I am able to update @lando/cli.
I've tried removing caches in ~/.lando/cache.
I've tried setting up an auth.json file to authenticate my github requests - but confess I'm not entirely sure where I need to place the auth.json file.
The problem occurs in the v3.23.1 version of lando and several versions prior to that. I generally keep lando up to date and it has been occurring for about a month.
My OS is Ubuntu 22.04 running through WSL2.
The text was updated successfully, but these errors were encountered: