Tom Rogers

@johanneslumpe Sorry, but no. I'm not an Obj-C dev. I can't trace or debug execution once it leaves the JS world. I see some code in Downloader.m that appears relevant,...

It's still a fact that bad `bytesWritten` is a bug that ought to be fixed. Yes, the promise resolves IFF the download completes, but without `bytesWritten`, it's impossible to know...

@NigelEarle Yes, the user experience is the same when the login flow is constructed manually. That's precisely why I filed this ticket: this package doesn't seem to substantially improve the...

This workaround worked for me on macOS 10.13.6: https://github.com/atom/atom/issues/1669#issuecomment-135503562 As is mentioned in another place, I had to mkdir the `~/Library/KeyBindings` directory.

@jhen0409 If you're using redux-persist, I suspect that's the cause of the contentious AsyncStorage calls. We gave up on redux-persist for now, because of this issue, and because there's a...

The solutions described here weren't working for me. I tried 1024, 2048, even 4096. In every case, the error said the limit has been exceeded by 466MP: ``` throw new...

More digging reveals that the return value (in my scenario) should be shaped like one of your Intervals: `{ lo: number, hi: number }`. _However_: it is not true that...

I'm not familiar with the term "hull," but the implementation of that function seems like it does what is needed. That said, it also seems like kind of a weird...

I think this ticket can be closed. The current iteration of the docs addresses my original concerns. Kudos! And thanks.

I imagine you could establish a timeout like 60 seconds. If the script hasn't completed in that time, assume it's an infinite loop and terminate it. Then, put that number...