Einar Nilsen-Nygaard

@Rajasekar0104 Please note that this will be rolled back on 3.2 as well.

@chadell, maybe. The fork is quite old, but I will look at bringing it up-to-date.

@MorningLightMountain713, this is happening as ncclient is trapping what it considers a non-fatal exception coming from Paramiko and logging it instead. Had ncclient not been doing this you would have...

@avazquezrd, there was no specific reason to not have this configurable. Please feel free to submit a PR with appropriate tests.

@sambhugit , agreed, if you need to connect concurrently with 10K devices from a single process then the thread count will be too high to be practical. I would also...

Closing this issue as no remedial actions need to be taken.

@CaiBIRen, not really enough details to give any advice or diagnosis...

@dineshbaburam91, having read the thread it's not clear to me why this is an `ncclient` issue, but I may have missed something. For example, if an XML payload contains text...

No feedback on examples requested. Closing for now.

@xietian511ok, if a device is not conformant with standards, we should **not** connect with it. I am reluctant to change the core implementation. However, you can perhaps use the Juniper...