零Rei
零Rei
It would be good to figure this out, but that probably involves rewriting some of the tests to run in child processes where the asynchronous context isn't being affected by...
Hey @Qard, I'd like to make this your problem if I could, since you wrote the original code. Under at least `[email protected]` and `[email protected]`, the promise tests show a bunch...
Probably a change in the last few releases of Couch, but in any case, had to make this change to get the scripts running properly.
AND ALSO GENERATORS AND ALSO MONGODB NEEDS MOAR WEBSCALE
This is a WIP: - [x] tests and documentation for `Abstract` (base class) - [ ] tests and documentation for `Reader` - [ ] tests and documentation for `Writer` -...
Using some clever instrumentation, I have traced all the calls to mkdirp for the root directory for a module being written by `fstream`. My gut tells me that it's doing...
When a caller hits [this stat failure](https://github.com/isaacs/fstream/blob/master/lib/writer.js#L284), it takes considerable sleuthing to figure out why the stat was even happening. Wrapping the error message up with some explanatory text would...