CLI: allow dispatch functions to return a Deferred #2826
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2826
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This will enable #2490 to run (async) Tor operations during
tahoe create-node --listen=tor
. Currently all CLI dispatch functions must finish synchronously.The file-operation subcommands, which use blocking
httplib
calls, must be run from unit tests underdeferToThread
. #2825 is about fixing that, but this ticket will do some cleanup that will help. Specifically it will move the deferToThread down intorunner.py
, using the thread only on the subcommands which really need it. After this is fixed, there should be no deferToThread calls in the unit tests.The branch is ready to land. It looks like there's one
deferToThread
left in the test suite:test_runner.RunBinTahoeMixin.run_bintahoe
usessubprocess.Popen
underneathdeferToThread
. I think this can be replaced with areactor.spawnProcess
, but I'm not 100% sure, and I don't want to go messing with it right now, so I'm going to leave that cleanup for another day.In 802cfc8/trunk: