Yoseph Maguire

@agilan2001 also please advise how you want to go about supporting this. Since it is an experimental feature in v15, we cannot just say "we support this feature". Is there...

ran into this issue. Google brought me to the original thread: https://github.com/microsoft/rushstack/issues/1029. And now I'm here. So is this still not supported? My error looks like: ``` --[ FAILURE: @azure/digital-twins-parser-generator...

Also, just a note: that's a terribly unhelpful error. Really no information to work off except a desperate Google attempt.

Thanks artikh for filing this issue. Could you please paste the code snippet in your `repro.zip` folder, since I don't want to open up a random js file from Github....

@artikh so is this a problem that the broker sends back a SUBACK with QoS level granted filled in, but then right after that emit's a close event to the...

maybe censure the keys 😄

looking into this. repro'd and debugging.

log from running repro: ```js Packet sent: {"cmd":"subscribe","subscriptions":[{"topic":"some-other-topic","qos":1}],"qos":1,"retain":false,"dup":false,"messageId":31113} mqttjs:client sendPacket :: writing to stream +2ms mqtt-packet:writeToStream generate called +302ms mqtt-packet:writeToStream generate: packet.cmd: subscribe +0ms mqtt-packet:writeToStream subscribe: packet: +2ms mqtt-packet:writeToStream subscribe:...

When the stream is closed because of the unauthorized error mqtt.js calls ```js this.stream.on('close', function () { debug('(%s)stream :: on close', that.options.clientId) flushVolatile(that.outgoing) debug('stream: emit close to MqttClient') that.emit('close') })...

sounds like doc update is in order. if you make a PR, I will approve it.