The Laughing Wolf

The error is persisting across multiple hosts. I can temporarily resolve the issue by changing the ID, but after enough restarts and reconnects, the error will appear again and I...

Given this behavior, we're unable to rely on this package for any real-world applications. I've used Bottleneck without problems before, and according to the documentation, this package is relied upon...

Also encountered this issue. I was also using `node-persist` as a sort of queuing mechanism, and I got a corrupted JSON file: `{"key":"downstream.updates.zendesk-ticket-fields.hubspot-company-changed","value":{"##########":{"zip":"*****"}}}*****"}}}` Looks like a previous update had changed...

I've read #4274 and understand the argument there. It makes good sense. However, the documentation still explicitly points to a page that describes behavior NOT matched by `xor`. The documentation...

@phapdinh Hello, I'm mentioning you because I see you've committed to Lodash recently, in #5427 . Please let me know if there's a better way to go about finding somebody...