duplicate settings in tahoe.cfg should produce an error #1684
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#1684
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?
If there are multiple lines for the same setting in
tahoe.cfg
(for example, multipleintroducer.furl =
lines), Tahoe will silently pick one of them. I think it picks the one later in the file. This is most likely a user error that should be reported. It can happen when you have commented settings and intend only one of them to be uncommented, but make a mistake, for instance.(I know this is just the standard behaviour of
ConfigParser.SafeConfigParser
, but it's still broken IMHO.)There is a minor backward-compatibility issue in that config files that worked accidentally will stop working if we make this an error. I still think it should be an error rather than a warning, though.
+1 on making duplicate settings be an error. Here's a recent patch which inspected the config file and stopped with an error if there was something fishy. The person working on this ticket might want to emulate this patch, including its unit tests: changeset:e5c4e83f4cfe3769.