suppress DeprecationWarning in tahoe --version output #1129
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#1129
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?
From /tahoe-lafs/trac-2024-07-25/issues/6184#comment:78742 :
The DeprecationWarning should have been suppressed.
source:src/allmydata/init.py contains code that is intended to suppress this warning, but says to do so only when it comes from twisted:
I think this should just be changed to a global filter, i.e. delete '
module=".*twisted.*",
'. This particular deprecation is not important and doesn't ever merit bothering any end-user.Attachment silence-basexception-warning.dpatch (1169 bytes) added
init.py: silence DeprecationWarning about BaseException.message globally.
(That attachment description should say
*init*.py
.)Attachment test-tahoe-version-no-warning.dpatch (1909 bytes) added
test_runner: test that 'tahoe --version' outputs no noise (e.g. DeprecationWarnings).
reviewed. +1. (I suggest that you
darcs amend --edit
the patch to append "fixes #1129" to it, and if you don't do so soon then I will.)In changeset:94bec75ddaddaaf5:
Hmm, actually the output in the description shows that the version of twisted is 8.2.0, so the unit test will be skipped (this matches the existing
test_client_no_noise
intest_runner.py
, but the latter is also skipped on platforms where we can't daemonize).Is the test valid when
Twisted < 8.2.0Twisted < 9.0.0, or will it give false-alarms?Sorry, I don't understand the question(s) in comment:78749.
Replying to zooko:
The [new test]source:src/allmydata/test/test_runner.py@4581#L51 is skipped if the Twisted version < 9.0.0. That's copying the skip condition in [test_client_no_noise]source:src/allmydata/test/test_runner.py@4581#L376. (The new test is not redundant with test_client_no_noise, because it can be run on Windows and the latter can't, and because it's testing a different command.)
I was wondering whether this skip is actually necessary. It might not be, since
tahoe --version
doesn't need to import very much of twisted.I don't know, but I don't mind skipping the test when Twisted < 9.
Replying to zooko:
OK, so the fix in changeset:94bec75ddaddaaf5 is sufficient.
In changeset:59e80b2ec92928bf:
Replying to david-sarah@…:
Typo in commit message; this should have referred to #1229.