aleaficionado
aleaficionado
In #406 I added a patch (apologies I'm not up-to-speed on using GitHub) where I changed the paws.common to use HTTR's retry capability (changed httr::VERB to httr::RETRY and used times...
Sorry not sure if the above was clear, but the patch should allow all requests (across all paws packages) to retry w/o additional coding logic (other than setting the config...
No problem. Hope all is well. The only throttle I've had with AWS was when writing hundreds of thousands of files at the same time to S3 from one of...
Hi, First of al great package. I don't think I had an older version of paws.common as I have never used R before submitting this issue, but I will check...
Hi, Sorry about taking time to reply to this. I got dragged into something else. Isn't max attempts the same as retry logic?
It just clicked. So the max_attempts option was not implemented. I agree there are some situations where you don't want to retry a request and there are cons to implementing...
I suspect the steps are: 1. connect 2. sever the connection on the network [e.g. assume the flow is Laptop->LAN->Internet->Redshift, the connection should be severed on a device on the...
You can use stv_sessions. I think the Postgres equivalent would be pg_stat_activity.