On Thu, 13 Nov 2014, at 17:01, Peter Westlake wrote:
>
>>> I've put in the dataReceived, and the answer box does*not*make it
>>> into the Protocol. There are two entries in
>>> protocol._outstandingRequests: {'2189': , '2188':
>>>
62810704], length 31
F..S.P@.@.U. . ..7.....0Zm.
)..}..jP.._answer..867d..status..True.. 16:19:33.542986 IP
wheezy-1.example.com.43517 > xenbuilder.example.com.8091: Flags [.],
ack 807050, win 296, options [nop,nop,TS val 62810705 ecr 696524413],
length 0 (etc)
Peter.
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
54538, 154331, 299, 8, 0, 0, 0. The last four
calls time out, which isn't surprising if that's how long they wait!
The full strace output shows descending runs of values, with some
omissions and duplicates. If this was C, it would be an uninitialised
variable for sure.
Peter.
poll([{fd=5
value counts down. Eventually it gets very close to zero. If
there is a burst of AMP activity around that time, there's a good chance
that the one of the poll() calls will time out.
How this leads to the data being lost is another question, but the
coincidence of events is too much to ignore.
f 2.7.8. The ticket has a comment
from 2011 saying it should work in Python 3.x (and the code does
look as though it should), and a suggestion from 2013 that it
should be closed.
So, how's that port to Python 3 going?
Peter.
___
Twisted-Python maili
On Mon, 17 Nov 2014, at 20:25, Glyph wrote:
>
>> On Nov 17, 2014, at 19:32, Peter Westlake
>> wrote:
>>
>> It's a known bug in Python!http://bugs.python.org/issue1038591,
>> "Python 2.3+ socket._fileobject handles EAGAIN with data loss".
>
>
ver have been
1038591
even if Twisted had used that bit of code, because that reads the data
in and
then loses it. So strace would have shown it being read.
I'll get some help from my local TCP experts, and let you know if I find
anything
out. In the meantime, thank you all for your patience an
the socket open on FD 0.
Now I grant that there's no need to pass /dev/null to the stdin of the
process. I should just leave 0 out of childFDs instead. But why does
this not work? lsof shows that the socket is on FD 3 in the parent
process, and the print statem
On Fri, 21 Nov 2014, at 14:08, Peter Westlake wrote:
> Found it!
>
> from twisted.internet.protocol import ClientFactory, Protocol,
> ProcessProtocol from twisted.internet import reactor
>
> devnull = open('/dev/null').fileno() print devnull
>
> factory
On Fri, 21 Nov 2014, at 19:26, Glyph wrote:
>> On Nov 21, 2014, at 15:13, Peter Westlake
>> wrote:
>>
>> I*am*missing something obvious. The file opened by open() immediately
>> goes out of scope. AAAUGH!
>
> So... back to square one? Or is this the solution
is operating at the same abstraction level and therefore less
> error-prone.
That's useful to know, thanks. I'll remember it for next time!
Peter.
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
for this purpose? A sort of
middleware (hate that word) to intercept transport events (including transport
formation, i.e. Endpoint.connect()).
I'm looking forward to being proven wrong on this as it will make my SOCKS work
easier, or else if this turns out to be interesting then I have more
101 - 112 of 112 matches
Mail list logo
