Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Docker for Mac loves burning my CPU. Even if I delete all images and containers and do a fresh reinstall and JUST have Docker for Mac running, I always see crazy CPU usage on my Late 2016 15" Macbook Pro.6
My shell was taking a really long time to start and I spent hours disabling every single plugin and trying to start it up without it to find out which one was the culprit.
Turns out it wasn't any of my plugins, it was NVM.
I spent hours trying to enable CORS on AWS Lambda through API gateway (it was supposed to be simple and Amazon had a nice tutorial) but it turns out that there's a known bug that makes Lambda Proxy Integrations not adhere to any setting in the API Gateway, you have to respond with the headers through the Lambda yourself.
Amazon now mentions this in the tutorial, but if you click "Enable CORS" in API Gateway, it'll show you green check marks and tell you that everything went fine, but you'll find that the Lambda does not respond with the CORS headers. They shouldn't even have "Enable CORS" as an option when you use their Lambda Proxy Integration.1