Mailman 3 August 2018 - Twisted

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com 19 Aug '18

19 Aug '18

1 0

[Twisted-Python] Fix link on trac for logging in
by Craig Rodrigues 18 Aug '18

18 Aug '18

Hi, If a user clicks on this link: https://twistedmatrix.com/trac/newticket They see this text: You are currently not logged in. You may want to do so <https://twistedmatrix.com/trac/login> now. The link on "do so" is wrong. *Can someone fix that link to point to the Github login link?* Ideally, this link: https://twistedmatrix.com/trac/login should redirect to: https://twistedmatrix.com/trac/github/login Because there seem to be various paths that users are hitting the first link and then getting confused when they can't log into Trac. -- Craig

2 4

[Twisted-Python] Partnership possibility with Twisted
by Alex Georgie 13 Aug '18

13 Aug '18

Hi everyone, I'm Alex from SeedAndDew. I was chatting with Moshe about SeedAndDew and whether Twisted would like to participate and he mentioned bringing it to the mailing list to get your opinions. SeedAndDew is a common subscription platform that allows users to contribute to a number of open source projects with a single subscription. The idea here is that it's a lot easier to get people to contribute $10/month to every open source project they work with than it is to get them to contribute $5/month for a specific project. The subscription revenue will be distributed based on the amount of time users spend reading documentation of the respective project which I anticipate will correspond well with actual use. So if a user spends 10% of their time reading the Twisted documentation, you get 10% of the subscription revenue. Our goal is to increase the pool of people who contribute to open source by removing the friction of having to manage subscriptions paid to specific projects and changing it as your stack and interests change. This would be a passive income source that doesn't require any further work outside of the initial integration. So far we have 10 projects including SQL Alchemy, RSpec, Bundler, Browsh and Parse. Does this seem like something you would be interested in? Thanks, Alex <http://mailstat.us/tr/opt-out?guid=yohzugwjkld0u3s> <http://mailstat.us/tr/t/dummy>

2 2

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com 12 Aug '18

12 Aug '18

1 0

[Twisted-Python] Tahoe 1.13.0
by meejah 08 Aug '18

08 Aug '18

ANNOUNCING Tahoe, the Least-Authority File Store, v1.13.0 The Tahoe-LAFS team is pleased to announce version 1.13.0 of Tahoe-LAFS, an extremely reliable decentralized storage system. Get it with "pip install tahoe-lafs", or download a tarball here: https://tahoe-lafs.org/downloads Tahoe-LAFS is the first distributed storage system to offer "provider-independent security" — meaning that not even the operators of your storage servers can read or alter your data without your consent. Here is the one-page explanation of its unique security and fault-tolerance properties: https://tahoe-lafs.readthedocs.org/en/latest/about.html The previous stable release of Tahoe-LAFS was v1.12.1, released on January 18, 2017. v1.13.0 fixes several problems with the magic-folder frontend, adds --json to more commands, adds the "tahoe status" and "tahoe magic-folder status" commands and some internal refactoring. It is also now possible to have multiple magic folders in a single Tahoe client. A long-standing feature to improve the share-placement algorithm ("servers of happiness") has been updated and merged. "tahoe backup" now reports progress. New clients can now be added to a grid using "magic wormhole" [14], a SPAKE2-based method of securely connecting two computers. This adds the "tahoe invite" command for a current grid-participant to invite a new client and a corresponding option "tahoe create-client --join" for the other side. These use a server at ``wormhole.tahoe-lafs.org`` currently operated by Least Authority. Please see ``NEWS.rst`` for a more complete list of changes. WHAT IS IT GOOD FOR? With Tahoe-LAFS, you distribute your data across multiple servers. Even if some of the servers fail or are taken over by an attacker, the entire file store continues to function correctly, preserving your privacy and security. You can easily share specific files and directories with other people. In addition to the core storage system itself, volunteers have built other projects on top of Tahoe-LAFS and have integrated Tahoe-LAFS with existing systems, including Windows, JavaScript, iPhone, Android, Hadoop, Flume, Django, Puppet, bzr, mercurial, perforce, duplicity, TiddlyWiki, and more. See the Related Projects page on the wiki [3]. We believe that strong cryptography, Free and Open Source Software, erasure coding, and principled engineering practices make Tahoe-LAFS safer than RAID, removable drive, tape, on-line backup or cloud storage. This software is developed under test-driven development, and there are no known bugs or security flaws which would compromise confidentiality or data integrity under recommended use. (For all important issues that we are currently aware of please see the known_issues.rst file [2].) COMPATIBILITY This release should be compatible with the version 1 series of Tahoe-LAFS. Clients from this release can write files and directories in the format used by clients of all versions back to v1.0 (which was released March 25, 2008). Clients from this release can read files and directories produced by clients of all versions since v1.0. Network connections are limited by the Introducer protocol in use. If the Introducer is running v1.10 or v1.11, then servers from this release (v1.12) can serve clients of all versions back to v1.0 . If it is running v1.12, then they can only serve clients back to v1.10. Clients from this release can use servers back to v1.10, but not older servers. Except for the new optional MDMF format, we have not made any intentional compatibility changes. However we do not yet have the test infrastructure to continuously verify that all new versions are interoperable with previous versions. We intend to build such an infrastructure in the future. This is the twenty-first release in the version 1 series. This series of Tahoe-LAFS will be actively supported and maintained for the foreseeable future, and future versions of Tahoe-LAFS will retain the ability to read and write files compatible with this series. LICENCE You may use this package under the GNU General Public License, version 2 or, at your option, any later version. See the file "COPYING.GPL" [4] for the terms of the GNU General Public License, version 2. You may use this package under the Transitive Grace Period Public Licence, version 1 or, at your option, any later version. (The Transitive Grace Period Public Licence has requirements similar to the GPL except that it allows you to delay for up to twelve months after you redistribute a derived work before releasing the source code of your derived work.) See the file "COPYING.TGPPL.rst" [5] for the terms of the Transitive Grace Period Public Licence, version 1. (You may choose to use this package under the terms of either licence, at your option.) INSTALLATION Tahoe-LAFS works on Linux, Mac OS X, Windows, Solaris, *BSD, and probably most other systems. Start with "docs/INSTALL.rst" [6]. HACKING AND COMMUNITY Please join us on the mailing list [7]. Patches are gratefully accepted -- the Roadmap page [8] shows the next improvements that we plan to make and CREDITS [9] lists the names of people who've contributed to the project. The Dev page [10] contains resources for hackers. SPONSORSHIP A special thanks goes out to Least Authority Enterprises [12], which employs several Tahoe-LAFS developers, for their continued support. HACK TAHOE-LAFS! If you can find a security flaw in Tahoe-LAFS which is serious enough that we feel compelled to warn our users and issue a fix, then we will award you with a customized t-shirt with your exploit printed on it and add you to the "Hack Tahoe-LAFS Hall Of Fame" [13]. ACKNOWLEDGEMENTS This is the eighteenth release of Tahoe-LAFS to be created solely as a labor of love by volunteers. Thank you very much to the team of "hackers in the public interest" who make Tahoe-LAFS possible. meejah on behalf of the Tahoe-LAFS team August 5, 2018 [1] https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.13.0/NEWS.rst [2] https://github.com/tahoe-lafs/tahoe-lafs/blob/master/docs/known_issues.rst [3] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/RelatedProjects [4] https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.13.0/COPYING.GPL [5] https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.13.0/COPYING.TGP… [6] https://tahoe-lafs.readthedocs.org/en/tahoe-lafs-1.13.0/INSTALL.html [7] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev [8] https://tahoe-lafs.org/trac/tahoe-lafs/roadmap [9] https://github.com/tahoe-lafs/tahoe-lafs/blob/master/CREDITS [10] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Dev [12] https://leastauthority.com/ [13] https://tahoe-lafs.org/hacktahoelafs/ [14] https://github.com/warner/magic-wormhole

1 0

[Twisted-Python] subunitreporter 18.7.5
by Jean-Paul Calderone 08 Aug '18

08 Aug '18

Hello all, I'm happy to announce a new project, subunitreporter <https://pypi.org/project/subunitreporter/>, which provides a reporter plugin for Trial which emits subunit v2 output. Twisted includes a subunit v1 reporter for Trial. However, the v1 output format must generally be converted to the v2 format before much can be done with it. Additionally, the reporter included with Twisted does not include timing information. The output generated by subunitreporter does include this information. One useful thing to do with a subunit v2 stream is convert it to junitxml and let CircleCI ingest it. This is precisely the reason I've written this reporter. You can see this in action on some recent Tahoe-LAFS builds. In all cases, builds now include a summary of the number of tests run. Additionally: On success <https://circleci.com/gh/tahoe-lafs/tahoe-lafs/438>, slowest test are reported. On failure <https://circleci.com/gh/tahoe-lafs/tahoe-lafs/379>, the failing tests and their failure details are summarized. Further analysis and reporting <https://circleci.com/build-insights/gh/tahoe-lafs/tahoe-lafs/master> is also done. I find this to be a nice development convenience when using CircleCI. Other build systems are likely to be able to use either the subunit v2 output or (like CircleCI) the equivalent junitxml which can trivially be produced from the subunit v2 output. My thanks to Least Authority TFA GmbH <https://leastauthority.com/> for sponsoring these specific Tahoe-LAFS infrastructure improvements as well as the subunitreporter project. Enjoy, Jean-Paul

2 1

[Twisted-Python] [ANN] txkube 0.3.0
by Jean-Paul Calderone 08 Aug '18

08 Aug '18

Hello all, I'm pleased to announce a new release of txkube, a Twisted-based library for interacting with Kubernetes using the HTTP API. The big news for this release is support for Python 3.6. Also included is support for multiple configuration files in the KUBECONFIG environment variable which allows for better configuration management practices. Here is an example of txkube usage, taken from the README: from __future__ import print_function from twisted.internet.task import react from txkube import network_kubernetes_from_context @react def main(reactor): k8s = network_kubernetes_from_context(reactor, u"minikube") d = k8s.versioned_client() d.addCallback( lambda client: client.list(client.model.v1.Namespace) ) d.addCallback(print) return d You can download txkube from PyPI <https://pypi.python.org/pypi> You can contribute to its development on GitHub <https://github.com/LeastAuthority/txkube>. Thanks to Least Authority TFA GmbH <https://leastauthority.com/> for sponsoring this development and to Craig Rodrigues for his efforts on Python 3 porting work. Jean-Paul Calderone <https://as.ynchrono.us/>

1 0

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com 05 Aug '18

05 Aug '18

1 0

[Twisted-Python] Why you are starting to see patch from me
by Barry Scott 04 Aug '18

04 Aug '18

I thought you might like a little background on why I'm starting to send in patches. The code base I'm working on uses Twisted 2.0 with lots of patches and some back ports for newer Twisted. We also use Nevow. The code started life a long time ago. I have been porting the code to use current Twisted. I have only needed to make two small patches to Twisted itself to port to 18.4. Tickets #9503 and #9504. Our code does use a lot of the private interfaces in Twisted. We know we are at risk of internals changing and breaking us, but the public interfaces do not allow us to implement the features of the product. Barry

2 1

[Twisted-Python] How do recommend I run epytext?
by Barry Scott 03 Aug '18

03 Aug '18

The tox checking does not cover the epytext checks it seems. How do you recommend I have epytext checked for a patch? Barry

2 1