Skip to content
This repository has been archived by the owner on Jun 28, 2024. It is now read-only.

Rate limiting should not trigger error messages #65

Closed
Ten0 opened this issue Nov 12, 2019 · 0 comments
Closed

Rate limiting should not trigger error messages #65

Ten0 opened this issue Nov 12, 2019 · 0 comments
Assignees
@serayuzgur
Milestone
0.4.6

Comments

@Ten0
Copy link

Ten0 commented Nov 12, 2019

I'm often hitting the following error:

StatusCodeError: 403 - "{\"message\":\"API rate limit excceeded for {my ip address}. blablabla authenticated requests blablabla\"}

This is especially true since we are several people using the extension on the same IP address.

I think rate limiting should not trigger these error messages so that we don't have to disable the extension to edit our Cargo.toml in case we hit a rate limit for some time.
@serayuzgur serayuzgur self-assigned this Nov 12, 2019
@serayuzgur serayuzgur added this to the 0.4.6 milestone Nov 12, 2019
serayuzgur added a commit that referenced this issue Nov 19, 2019
@serayuzgur
- Should not convert single to double quotes [#66](#66)
7ae6865 
- Rate limiting should not trigger error messages [#65](#65)
- Fetch Errors and constant error messages when viewing Cargo.toml with conflicts [#61](#61)
- Alert always happen when I add deps to Cargo.toml [#59](#59)
- `No versions found` error should be less intrusive [#58](#58)
- alternative registries are not taken into account [#41](#41)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@serayuzgur serayuzgur

Labels
None yet
Projects
None yet
Milestone
0.4.6
Development

No branches or pull requests
2 participants
@serayuzgur @Ten0