Niels Abildgaard

You are correct, currently anything other than a code 200 is treated as an error. From W3Cs [documentation on status codes](http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html): > The requested resource resides temporarily under a different...

This seems to be a previously reported issue (with GCM): - https://groups.google.com/forum/#!topic/android-gcm/WwEg6buc-K0 - http://stackoverflow.com/questions/15037454/io-exception-while-accessing-google-cloud-message I don't see any documentation on how to handle it. I assume we could just re-run...

Just to clarify: I am very willing to do a PR for this, if it is within scope of this package :smile:

Hey, if there's anything I can help with to move this forward, I would love to contribute, but don't really know how :smile: (been using express since 2014, pretty familiar...

Related to this, it would be interesting to know what the policy is towards assertions in general: do you plan on adding more, or are we to make do with...

I was about to open a PR doing the same thing --- strong support from here 👍, we are currently extending the error serializer in all projects to support this.

I use pino for a bunch of projects, but the two aren't exactly equivalent, and there are plenty of situations where the cost of migrating is higher than the benefit...

Switching to [@dataui/crud](https://www.npmjs.com/package/@dataui/crud) as @ckaeslin suggests fixed this for me. The problem is an unmaintained, unofficial package that has fallen out of sync with nestjs. I personally took over a...

@geek-sajjad this repo isn't maintained anymore. See the latest comments and switch to [@dataui/crud](https://www.npmjs.com/package/@dataui/crud)

It seems that the problem is recursion using promises which, for zip files with lots of entries, increases the size of the big promise object to a point breaking the...