nicolasburtey
nicolasburtey
mostly done. still need a fibonacci backoff when an account has been temporarily suspend after too many attempts
this could be a good security improvement on the login() api. more documentation: https://github.com/animir/node-rate-limiter-flexible/wiki/Overall-example#dynamic-block-duration
@vindard have we adapted the memo threshold limit for USD wallet? if yes you can close this PR I guess
stale PR that is worth looking at: https://github.com/GaloyMoney/galoy/pull/148
logs format from nginx (default from helm): log_format upstreaminfo '$remote_addr - $remote_user [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" $request_length $request_time [$proxy_upstream_name] [$proxy_alternative_upstream_name] $upstream_addr $upstream_response_length $upstream_response_time $upstream_status $req_id';
this is still happening. sometime for probe that are taking a long time. sometimes also for mainQuery that return in a few hundred ms
@vindard I think this one has been completed?
we could make this a little bit more generic. I see two different options: - we could have a list of the other that should not be in contact. maybe...
note: this issue has now been resolved with the refactoring, but all the previous BBW transaction has the marketing user as a context. this could be cleaned up with a...
@UncleSamtoshi can you have a look once the facade is merged?