make the error message more helpful in case of no 'tahoe' alias #681
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#681
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?
Hi,
I'm getting this error on OS X 10.5.2 when trying to run any command minus start/stop and create-*. Anyone know why this might be?
Thanks!
Thanks for the bug report, prmr. I'm sorry that it fell by the wayside for four months -- I don't know if I ever noticed this ticket before now. I'm changing the title to reflect what I think is the issue here -- that the error message when there is no alias registered for 'tahoe' should be more helpful and explain that the
tahoe stats
command expects either a dircap or an alias on the command-line, or else for there to be a dircap registered under the default 'tahoe' alias in the aliases file.I'm also marking this ticket as "easy" -- a young hacker who wants to get into Tahoe-LAFS hacking should be able to fix this ticket easily enough even if they aren't familiar with the codebase.
Unable to run some commandsto make the error message more helpful in case of no 'tahoe' aliasI'm getting a different exception (Tahoe 1.5.0 r4044 with Python 2.6 on Windows Vista), but I think it's probably the same issue:
Duplicate of #939 (actually the other way around, but that ticket has more information).
The error in comment:70678 wasn't the same issue; it was due to
--node-directory
not being set (on Windows there is no default node directory when the registry entry set by the allmydata.com client is not present). I'll open another ticket for that.