Markus Unterwaditzer

@jeaye I'd argue that one-to-one ports from C into Rust would barely take advantage of the new language, since a main selling point of Rust is that you don't have...

> Let me know if you have any implementation suggestions; otherwise it will probably be a decorator. If you need to run multiple tests twice, perhaps check out fixture parametrization...

@danielkhan can you elaborate what you're seeing and provide full response headers and data?

in an offline discussion it turned out this is about API calls to Sentry (`/api/0/`), not store API calls (`/api/n/`). This probably warrants broader discussion in `#discuss-api` but as far...

Seems like this is actually documented at https://docs.sentry.io/api/ratelimits/ On Thu, Aug 4, 2022 at 10:42 AM Daniel Khan ***@***.***> wrote: > @AniketDas-Tekky can you provide an > example of what...

there is no quota for API calls like this

@danielkhan We have two APIs: The APIs sdks talk to to submit data (`/api/123/{store,envelope}/` where 123 is the project id, served by Relay), and the APIs the web UI (and...

okay, I'm unassigning ecosystem from this for now because this customer request is about sdk requests, not "the API" as we typically call the endpoints we use for querying data.

@fpacifici We have integration tests that ended up not testing anything because they are using the mock indexer (which doesn't have rate limits) together with mocked/stubbed fetch results coming from...

@fpacifici had to do a double-take on your first post, if I understood it right then it's actually really simple and https://github.com/getsentry/sentry/pull/36669 is basically it