AssertionError on DELETE when child links point to yourself #979
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#979
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?
USSJoin accidentally made a directory with all of its child links pointing to itself:
At some point he got an AssertionError, attached in HTML format.
Attachment error.html (7092 bytes) added
From the stack trace it looks like USSJoin was attempting to delete one of the child links when it goes this assertion failure.
Making such a directory isn't a problem in itself; this definitely looks like a bug in the webapi handling of DELETE.
AssertionError when child links point to yourselfto AssertionError on DELETE when child links point to yourselfThe assertion that failed is
assert self.parentnode and self.name
in DirectoryNodeHandler's [render_DELETE method]source:src/allmydata/web/directory.py#L140, i.e. eitherself.parentnode
orself.name
is falsy. Those fields are only set in the constructor, which is only called from [make_handler_for]source:src/allmydata/web/directory.py#L42, so we're looking for a call to make_handler_for with a missing or falsyparentnode
orname
argument. But there are quite a few calls to that, and the necessary context isn't on the reported stack trace.I can see how you might get this error by trying to DELETE
.../uri/URI:...
, I think -- are we sure that USSJoin didn't attempt to do that?The testgrid is down atm; I'll try some tests of this when it comes back up.