Austin Cawley-Edwards

It's just for discussion, sorry for the confusion -- dependable has an update-by-rebase feature using that comment. The same could be done with this [GitHub action.](https://github.com/cirrus-actions/rebase) That makes sense about...

Thanks for the detailed notes @chdsbd ! I probably don't have a chance to create a PR for a few weeks at least, so if anyone wants to take this...

Fixed this by setting the `parseBody` option to false, though I still believe that it should be either: a) enforced by default b) empty bodies should be translated to `""`...

Is it possible to bring this issue back up? It would be great if tags published on npm were also tagged and released here on GitHub.

Would you accept a PR for this? What are the situations where the reverse format applies?

Ah, `DeferCleanup`, genius. Thanks for that. I'll put in a PR for the lock asap :)

I'm actually not sure if I have the knowledge to finish the PR — it seems we need to lock more than just the append to the report entries, though...

Ah, the done channel makes sense when you break it down. I've looked at the fix and it makes sense too, once everything else is synchronized. Thanks for digging in...

I think newer versions of the Chart use `proxy.tls.enabled=false` instead: https://hub.kubeapps.com/charts/stable/kong

I've also seen this when scrolling: ``` Error: Authorization Exception at respond (/home/node/app/node_modules/elasticsearch/src/lib/transport.js:308:15) at checkRespForFailure (/home/node/app/node_modules/elasticsearch/src/lib/transport.js:267:7) at done (/home/node/app/node_modules/http-aws-es/connector.js:48:7) at IncomingMessage.cleanUp (/home/node/app/node_modules/http-aws-es/src/node.js:20:7 { status: 403, displayName: 'AuthorizationException', message: 'Authorization Exception',...