S3 cloud container AttributeError when retrying an operation: S3Container instance has no attribute '_reactor' #2206
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#2206
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?
The retry handling for S3 containers in the cloud backend is broken.
In /tahoe-lafs/trac-2024-07-25/issues/7141#comment:27, we have a traceback ending with:
This is a bug introduced during the refactoring that added
allmydata.storage.backends.cloud.cloud_common.CommonContainerMixin
.self._reactor
is now set in the constructor inherited fromCommonContainerMixin
, butS3Container
does not inherit fromCommonContainerMixin
and so does not call that constructor.Note that this is a classic example of the kind of error that would be caught by static typing but not necessarily by testing. (It does show that our test coverage for the S3 container is poor, which we knew about.)
Pull request at https://github.com/LeastAuthority/tahoe-lafs/pull/4.
The fix was in https://github.com/tahoe-lafs/tahoe-lafs/commit/de8b40188b67714a2a000206402a7458d6e55c68 and https://github.com/tahoe-lafs/tahoe-lafs/commit/e0ffe8bfcdb3f15f8e83d6472e058fa681bbe2a6 on the 1819-cloud-merge branch.
Milestone renamed
renaming milestone