Mailman 3 December 2016 - Twisted

[Twisted-Python] memory leaks
by Glyph Lefkowitz Dec. 6, 2016

Dec. 6, 2016

Following up on a Stack Overflow question from some time ago, http://stackoverflow.com/questions/40604545/twisted-using-connectprotocol-t… since the submitter added a minimal reproducer, I used Heappy https://pypi.org/project/guppy/ to look at memory sizing, and seeing large numbers of Logger instances and type objects leaking when using client endpoints. It was not immediately obvious to me where the leak is occurring though, as I was careful to clean up the Deferred results and not leave them in a failure state. I am hoping that I can entice someone else to diagnose this far enough to actually file a bug :-). -glyph

4 6

Re: [Twisted-Python] trac deployment (was: memory leaks)
by Jean-Paul Calderone Dec. 6, 2016

Dec. 6, 2016

On Tue, Dec 6, 2016 at 1:58 AM, Glyph Lefkowitz <glyph(a)twistedmatrix.com> wrote: > > Thanks! > > By "Fixed" I take it you mean rolled back, via: > > trac@dornkirk:~$ ./virtualenv/bin/pip freeze | grep Trac== > Trac==1.0.13 > > > and > > https://github.com/twisted-infra/braid/commit/ > c2d393fd501c6464b1b475eff214cab64f13ee2a > > > Don't get me wrong, I'm not complaining :). This is certainly the right > thing to do for now. But I'm wondering if you know what's wrong with 1.2 > so we can upgrade soonish? > > Is the braid trac service also fixed - or does the next person who tries to update the deployment need to watch out for this same failure mode? Jean-Paul > -glyph > > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python(a)twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > >

2 2

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com Dec. 4, 2016

Dec. 4, 2016

1 0

[Twisted-Python] continuous integration update
by Glyph Lefkowitz Dec. 3, 2016

Dec. 3, 2016

Hi all, On Github, the process was supposed to be that we push any 3rd-party contributor branches to the buildbots before doing a final merge. However, we (myself included, I think) have been landing PRs without doing that first. In order to ensure that the process is followed, I've added a representative sample of buildbot status checks - specifically, buildbot/osx10.10-py2.7, buildbot/freebsd10-py3.5, and buildbot/freebsd10-py2.7 to the required list. Additionally, I think I'd like to take our Mac builds off of Travis. They're still in the allow_fail section, so they haven't been blocking merges, but a Travis build can't complete (and therefore register as "succeded") without them. Given the repeated OS X related incidents on Travis (see here https://www.traviscistatus.com/incidents/nq0sf0srvx8s and here https://www.traviscistatus.com/incidents/3d430hxd59ft here https://www.traviscistatus.com/incidents/06xg686x7wgw and here https://www.traviscistatus.com/incidents/w82t22dlpntr and here https://www.traviscistatus.com/incidents/j7ttlsnbkf33 if you haven't been personally affected) the OS X builds have been responsible for something like 90% of our build times and have prevented me from making a lot of progress this week. I've submitted a PR for this at https://github.com/twisted/twisted/pull/614 which hopefully someone can review and merge if they agree. Thanks, -glyph

1 1

[Twisted-Python] future directions for Deferred
by Glyph Lefkowitz Dec. 1, 2016

Dec. 1, 2016

Since this is of potentially very broad interest within the Twisted maintainer team and development audience, those on the mailing list may want to read this github comment <https://github.com/twisted/twisted/pull/590#issuecomment-264070327> about ongoing discussions about future development of Deferred. -glyph

1 0