[Twisted-Python] Weekly Bug Summary
Bug summary __ Summary for 2014-08-17 through 2014-08-24 Opened Closed Total Change Enhancements: 5 1 1232 +4 Defects: 2 2749 +0 Tasks: 0 0 98 +0 Regressions: 2 0 8 +2 Total: 9 3 2087 +6 |== Type Changes |== Priority Changes |== Component Changes |Defect: +0 |High:+0 |Core: +5 |Enhancement: +4 |Normal: +6 |Trial: +0 |Regression: +2 |Web:+0 |Words: +1 Total Tickets Open Tickets New / Reopened Bugs __ = High = [#7561] Traceback attached (opened by ahch00) (CLOSED, invalid) enhancement core http://twistedmatrix.com/trac/ticket/7561 = Normal = [#7558] Get More Evidence From Liftderma (opened by raviborn2rock) enhancement core http://twistedmatrix.com/trac/ticket/7558 [#7559] `trial -j` exits suddenly and without any notice when running subunit-based tests (opened by jonathanj) defect trial http://twistedmatrix.com/trac/ticket/7559 [#7560] IRCClient.ctcpUnknownReply in twisted.words.protocols.irc should handle arbitrary CTCP queries (opened by eeshangarg) enhancement words http://twistedmatrix.com/trac/ticket/7560 [#7562] twisted.python.usage catches unrelated TypeError (opened by rwall) defect core http://twistedmatrix.com/trac/ticket/7562 [#7563] Some twisted.python.logger submodules are not installed on Python 3, breaking Twisted on Python 3 (opened by itamarst) regression core http://twistedmatrix.com/trac/ticket/7563 [#7564] Building Muscle With Body Building Proteins And Supplements (opened by soziroy1) enhancement core http://twistedmatrix.com/trac/ticket/7564 [#7565] What Is Lean Body Mass And How To Build It (opened by soziroy1) enhancement core http://twistedmatrix.com/trac/ticket/7565 [#7566] port twisted.python.systemd to python 3 (opened by PyroDevil) regression webhttp://twistedmatrix.com/trac/ticket/7566 Closed Bugs __ = High = [#7561] Traceback attached (opened by ahch00, closed by exarkun, invalid) enhancement core http://twistedmatrix.com/trac/ticket/7561 = Normal = [#7557] Use maybeDeferred for decode operation in HTTPAuthSessionWrapper (opened by alexzotov, closed by exarkun, invalid) defect webhttp://twistedmatrix.com/trac/ticket/7557 [#7556] twisted trial imports module twice, causing duplicate calls to ffi.verify (opened by vanandel, closed by exarkun, invalid) defect trial http://twistedmatrix.com/trac/ticket/7556 Ticket Lifetime Stats __ Oldest open ticket - [#50] conch command-line client doesn't work in win32 (since 2003-07-12 14:41:06). Newest open ticket - [#7566] port twisted.python.systemd to python 3 (since 2014-08-23 12:13:39.965882). Mean open ticket age: 1386 days, 10:40:22.843312. Median: 1142 days, 14:36:41.712051. Standard deviation: 1022 days, 14:42:15.237781. Interquartile range: 1607 days, 14:12:54. Mean time between ticket creation and ticket resolution: 640 days, 11:12:09.637352. Median: 100 days, 6:06:42. Standard deviation is 907 days, 11:02:29.069921. The interquartile range is 1017 days, 8:35:06. Mean time spent in review: 102 days, 12:39:47.967505. Median: 5 days, 6:33:46. Standard deviation: 456 days, 8:50:27.844124. Interquartile range: 23 days, 12:11:35. Mean number of times a ticket is reviewed: 1.9331963001. Median: 1 Standard deviation: 1.51908869006. Interquartile range: 1. Contributor Stats __ In the last 4 weeks, 17 unique ticket reporters 2 unique ticket reviewers 2 unique ticket resolvers In the last 24 weeks, 58 unique ticket reporters 22 unique ticket reviewers 17 unique ticket resolvers In the last 48 weeks, 107 unique ticket reporters 32 unique ticket reviewers 23 unique ticket resolvers ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
Re: [Twisted-Python] running twisted with supervisord -- logging question
Jonathan, On 24 Aug 2014, at 1:46, Jonathan Vanasco wrote: Thanks for the insight. I was stupid and didn't include my code. I don't actually want supervisor to handle the logging. I wanted to have this app's logs in /var/log/myapp-twisted/twisted.log I just can't figure out how to make this happen. i've been playing with different permutations of twistd commands, redirect_stderr and stdout_logfile, and haven't found the right balance I would strongly urge you to do what Christopher told you, and not just for Twisted but in general. Logging everything to stdout/stderr and then using some proper system tool to catch and process that instead of the finicky stdlib (or Twisted’s for that matter) logging will save you a lot of headaches and gain some love if you work with ops people. Another alternative is using syslog which is directly supported by twistd. —h ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
Re: [Twisted-Python] Twisted WebSockets Branch
Hi Rob, if your main concern is robust WebSocket on Twisted, why not use Autobahn (https://pypi.python.org/pypi/autobahn) ? Autobahn supports wrapping arbitrary stream-based protocols on top of WebSocket, with full support for advanced features like WebSocket compression and auto-fragmentation plus Twisted endpoints: https://github.com/tavendo/AutobahnPython/tree/master/examples/twisted/websocket/wrapping Note: Wrapping arbitrary stream-based protocols in WebSocket requires proper WebSocket subprotocol negotiation and handling. Autobahn follows the scheme established by https://github.com/kanaka/websockify for which you find e.g. JS libraries running in a browser. Autobahn also supports running WebSocket as a resource in a Twisted Web resource tree: https://github.com/tavendo/AutobahnPython/blob/master/examples/twisted/websocket/echo_site/server.py Disclosure: I wrote this stuff. So I am biased;) Glyph at one point mentioned that he likes to see basic WebSocket support built into Twisted. Bringing the branch to the full level of Autobahn rgd. features, compliance, robustness etc will be a lot of work though. Merging Autobahn into Twisted is unlikely to happen / doesn't make sense for different reasons I guess. /Tobias Von: twisted-python-boun...@twistedmatrix.com [mailto:twisted-python-boun...@twistedmatrix.com] Im Auftrag von Rob Oakes Gesendet: Freitag, 22. August 2014 04:24 An: twisted-python@twistedmatrix.com Cc: roa...@gurulabs.com Betreff: [Twisted-Python] Twisted WebSockets Branch Dear Twisted Developers, As a quick introduction, my name is Rob Oakes. I'm the lead developer for a company called Guru Labs. I'm writing for two reasons: # Reason 1: Thank You First and foremost, I'm writing to express thanks for creating an excellent framework. We use Twisted extensively in our infrastructure, and it is typically our go-to tool for any sort of custom server. The other two reasons have to do with some questions about the development of Twisted. Before I dive into those, however, let me provide some background. For the better part of a year, we've been using some code out of the websockets (twisted.web.websockets.WebsocketsResource) branch to wrap a trio of custom protocols we use in one of our web based products. I know that the code is still pre-release, but we've generally found it to be stable and work very well. # Reason Two: Websockets Development This brings me to the second reason I'm writing. Over the past year, it seems as though the development on the Twisted websockets branch has stalled. We would like to unstall it. For this reason, Guru Labs would be interested in: 1.) Contracting with one of the core Twisted devs of Twisted who might be interested in finishing the implementation of the websockets wrappers (resolving the issues described in ticket 4173) or another party. We are happy to pay hourly rates, set a bounty, make a donation to the Twisted project ... whatever. A stable implementation of websockets available in Twisted Web is a priority to us, and if it's a matter of money, we are happy to throw money where it might be needed. (If this of interest, please contact me off-list at roa...@gurulabs.commailto:roa...@gurulabs.com.) or 2.) Assigning a Guru Labs developer (probably me) who might complete the work. I've been studying the issues which are still open (specifically 4173), and the various branches associated with websocket development (websocket-4173-3 and websocket-4173-4) and it seems that most of the major concerns are related to the manner in which websocket connections are closed. Assuming that someone else doesn't step forward ... I've already merged the most recent version of trunk with these branches, but I've found myself with several questions on how to best continue with the work. a. Which of the two websocket branches should be used as the basis for new work? On GitHub, websocket-4173-4 is marked as closed with a note telling the contributor to see the contribution guidelines. There are also several additions to the code which do not follow Twisted conventions (as I understand them). The last set of commits also seem to come from approximately the same time. websocket-4173-4 includes code which attempts to resolve issues noted in 4173 that is not present in 4173-3, but there aren't really any comments to determine if this should be incorporated or not. At this point, I'm really not familiar enough with the code to draw my own conclusion. b. In general, the protocol wrapper seems to work quite well. However when merged with the most recent version of trunk (post twisted 14), I've been seeing frequent unhandled deferred errors. The most common is: twisted.internet.error.ConnectionLost: Connection to the other side was lost in a non-clean fashion: Connection lost It happens when: * Connections are closed from the server, using transport.loseConnection * Connections do not transmit a close frame
Re: [Twisted-Python] Twisted Trac
On 16 Jul, 06:02 pm, alex.gay...@gmail.com wrote: Hi all, A short while ago Twisted's trac installation was changed to reject new tickets from anyone except a special white listed group. As of yesterday I have reverted this change, (and turned the spam filter back on). If you experience any issues trying to post, or notice and spam, please feel free to reach out to me. Hi Alex, I notice some spam has started to get through. See the latest bug summary email. Jean-Paul ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
