Client closes connection instead of starting tls

[quickdudley]

I've been having trouble getting blather to reliably connect to prosody with tls. Sometimes blather connects successfully; but most of the time it ignores the starttls tag. This is the full conversation between client and server before blather closes the connection:

<stream:stream to='localhost' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0' xml:lang='en'><?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xml:lang='en' from='localhost' id='edf4035a-6a36-44d1-b94a-9cbd31c4e9cd' version='1.0' xmlns='jabber:client'><stream:features><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>SCRAM-SHA-1</mechanism></mechanisms><starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/><auth xmlns='http://jabber.org/features/iq-auth'/></stream:features></stream:stream></stream:stream>

Once one connection has exhibited this behaviour: no future connection from the same ruby process will proceed correctly. I'm able to connect successfully by restarting the ruby process about 5% of the time; and seem to have a slightly higher success rate if I have recently rebooted my operating system.

[quickdudley]

Issue seems to go away when I increase the timeout passed to Blather::DSL#setup.