ratelimit | A Go blocking leaky-bucket rate limit implementation

so as error indicates this is more to do not with python library but underlying web api error, via documentation link code=-2015 ("Invalid API-key, IP, or permissions for action.") now given you are getting some data back and just not for client.get_all_tickers() my guess would be permissions issue. to dig into issue will need to understand more from that doc site to better understand why getting error

I found the problem and I'm posting it here for anyone who might struggle in the future. It all came down to a simple configuration. In AWS SQS the queue I am working with has a configured DLQ (Dead-Letter Queue) and Maximum receives set to 4. According to the SQS docs

The Maximum receives value determines when a message will be sent to the DLQ. If the ReceiveCount for a message exceeds the maximum receive count for the queue, Amazon SQS moves the message to the associated DLQ (with its original message ID).

Since this is an infra configuration, it overwrites any Laravel parameters you might pass to the job. And because the message is simply removed from the queue, the processing job does not actually fail, so the failed method is not executed.

As far as I know, there is no way to reference the UsagePlan created as part of your Api.

However, you can create UsagePlan outside of ApiGatewayApi as a separate resource, and associate it with your ApiGatewayApi. Then you can easily reference it in your UsagePlanKey:

I think you need to write code [ return response('Custom response...', 429); ] in functions.

I suspect the Android emulator might be interfering with you here. I’ve seen issues with it misbehaving, particularly on Windows.

https://issuetracker.google.com/issues/119027639

If you'd like to workaround, consider changing your server to use something other than Connection: close to terminate your response body. Perhaps chunked encoding or a content-length header.

I would propose to take a look in the RateLimiter direction. Maybe it does not work as expected, depending on the number of requests your application does over time. From the Javadoc for Ratelimiter: "It is important to note that the number of permits requested never affects the throttling of the request itself ... but it affects the throttling of the next request. I.e., if an expensive task arrives at an idle RateLimiter, it will be granted immediately, but it is the next request that will experience extra throttling, thus paying for the cost of the expensive task." Also helpful might be this discussion: github or github

I could imaginge there is some throttling adding up or other effect in the RateLimiter, i would try to play around with it and make sure this thing really works the way you want. Alternatively, consider using Spring @Scheduled to read from your queue. You might want to spice it up using embedded JMS for further goodies (message persistence etc).

You are trying to use nullish coalescing (??) on an unsuported version of Node. Nullish coalescing is supported from Node v14 and up.
For now the simple alternative is ||, unless you upgrade your version.

The issue is resolved by returning a new instance of the message handler each time is invoked by the configureHandler delegate. As per the documentation given in this link it's mentioned there as

The configureHandler delegate should return a new instance of the message handler each time it is invoked.

So the final code goes like this

ConfigureServices Method

After analysing your code I have found the issue in naming the form controls.

So inside the Login form you have changed the email and pasword to login_email and password login_password inside the form. So when ever you send Login request to application AuthenticatedSessionController validate your request by using LoginRequest.

Since you have changed filed names. It will always give the validation errors. But you have not displayed the validation error. Thats the reason you cannot find the issue.

Changing from login_email to email and login_password to password will fix the issue.