manhole should be either tested or removed #2367

New Issue

tahoe-lafs · 2015-01-27T17:34:25Z

daira commented

2015-01-27 17:34:25 +00:00

No description provided.

tahoe-lafs added the

labels 2015-01-27 17:34:25 +00:00

tahoe-lafs added this to the undecided milestone 2015-01-27 17:34:25 +00:00

tahoe-lafs changed title from ~~add tests for manhole~~ to manhole should be either tested or removed

2015-02-05 16:39:38 +00:00

Brian Warner <warner@lothar.com> commented

2016-04-07 00:01:04 +00:00

In 8279d91/trunk:

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

In [8279d91/trunk](/tahoe-lafs/trac-2024-07-25/commit/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 ```