Brandon Zacharie

While I do see the warning when using v6, compilation proceeds without error. Modules inherit this from node. AFAIK, as of v7 node links to libc++ instead of libstdc++. I...

This is handled by https://github.com/barrysteyn/node-scrypt/pull/119

I think this may be caused by #185

AFAIK, there's no instance where a callback of `verifyKdf` is passed an error ([see here](https://github.com/barrysteyn/node-scrypt/blob/v5.4.0/src/node-boilerplate/scrypt_kdf-verify_async.cc)). However, it's probably there to keep the library future proof and in line with the...

I've been struggling with this for a couple of days. I haven't been able to find a way to prevent table view crashes when applying updates that originate from a...

Any update on this? I think this should be labeled `bug` rather than `enhancement` and given a higher priority because the changes in notifications are unusable. Personally, I've only been...

I first ran into trouble with notifications in July last year. Our app makes heavy use of applying updates that originate from a realm modified on a background thread and...

I just tried the demo project from @TeunVR with Realm 3.13.0 and it still crashes. However, that specific issue can be resolved with by wrapping tableview update calls with `DispatchQueue.main.async`...

I see the need you have here and thanks for taking the time to find out what's going on. I agree that it's troublesome to see what went wrong without...

An `error` event would also help resolve #7 since we could publish an error when `logfile` or any other incompatible configuration is found.