It already helps to know this isn't normal behavior. My code is self-contained in a single file and I can add a main for testing. However it's far from minimal. The problem doesn't occur right away - only after several channels have been opened/closed with a persistent connection. I'll continue to work and try to minimally pin it down but as you know it's difficult with asynchronous operations on several hosts. It can run 100's of channels on multiple hosts without a problem or the problem can occur in the first five minutes. For now, I just add a canceller method on downstream deferreds and try again.
Steve > On Jul 6, 2017, at 5:14 AM, Adi Roiban <a...@roiban.ro> wrote: > > On 5 July 2017 at 23:00, Stephen McRoberts <ste...@mcroberts.org> wrote: >> I'm looking for suggestions why the channel key would be missing after it >> was just opened. >> I use persistent connections with a timeout but the timer is reset every >> call so it stays open. > > [snip] > > As suggested by Glyph. > Please provide a complete minimal example which can be used to > reproduce this behaviour. > > http://sscce.org/ > > I am happy to help with any SSH related bugs. > > -- > Adi Roiban > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
