Thom Nichols

I hit this bug as well, it is triggered by `lex-parser`: https://github.com/zaach/lex-parser/blob/master/package.json#L9-L12 Confirmed this is spec for package.json format: https://nodejs.dev/learn/the-package-json-guide#repository

This project looks dead (no commit activity in a _very_ long time.) And this issue is completely blocking S3 connectivity. Anyone know of a drop-in alternative or maintained fork? **Edit:**...

I was wondering this too. The example linked by @lenzenc looks pretty straightforward but it's not clear how to integrate that with this plugin. Would be nice to get a...

Referring to [subelements documentation](http://docs.ansible.com/ansible/playbooks_loops.html#looping-over-subelements) it appears the correct form should be: ``` with_subelements: - "{{ network_bridge_interfaces }}" - ports ```

> the issue occurred when a server responded with an error without reading the stream @rawmind This tracks with what I'm seeing: in my case the intermittent failure I encounter...

> can't replace the library's default and mandatory GetNext's OID selection mechanism with your own handler to manage the whole GetNext operation, and so your MIB would require at least...

Is this a duplicate of #18?

Either way, I'm going to suggest for anyone using this library in a production environment either migrate to [bonjour-service](https://www.npmjs.com/package/bonjour-service) or [@homebridge/ciao](https://www.npmjs.com/package/@homebridge/ciao). This project is unmaintained, it has not seen a...

Came across jmdns/jmdns#84 which gives some hints as to the cause. It's probably originating here: https://github.com/mafintosh/multicast-dns/blob/master/index.js#L53-L55 Although I'm not clear as to why the OS is emitting the ENODEV error.

As a stopgap, I think I can add the following to prevent the `error` event from crashing node: ```javascript b = bonjour(); b._server.mdns.on('error',err => console.error('mdns server', err)); ``` *EDIT*: actually...