[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2367: manhole should be either tested or removed

[Tahoe-LAFS]

#2367: manhole should be either tested or removed
------------------------+-------------------------------
     Reporter:  daira   |      Owner:  daira
         Type:  defect  |     Status:  closed
     Priority:  normal  |  Milestone:  undecided
    Component:  code    |    Version:  1.10.0
   Resolution:  fixed   |   Keywords:  tests manhole ssh
Launchpad Bug:          |
------------------------+-------------------------------
Changes (by Brian Warner <warner@…>):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8279d919f32a30a408951bdcb6e4461957b8303c/trunk"
 8279d91/trunk]:
 {{{
 #!CommitTicketReference repository="trunk"
 revision="8279d919f32a30a408951bdcb6e4461957b8303c"
 remove "manhole" (ssh-accessible REPL)

 This little-used debugging feature allowed you to SSH or Telnet "into" a
 Tahoe node, and get an interactive Read-Eval-Print-Loop (REPL) that
 executed inside the context of the running process. The SSH
 authentication code used a deprecated feature of Twisted, this code had
 no unit-test coverage, and I haven't personally used it in at least 6
 years (despite writing it in the first place). Time to go.

 Also experiment with a Twisted-style "topfiles/" directory of NEWS
 fragments. The idea is that we require all user-visible changes to
 include a file or two (named as $TICKETNUM.$TYPE), and then run a script
 to generate NEWS during the release process, instead of having a human
 scan the commit logs and summarize the changes long after they landed.

 Closes ticket:2367
 }}}

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2367#comment:2>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage