blackmatch fuse doesn't know what to think about immutable directories #894
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
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#894
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
As reported by François over on comment:73442:
this log fragment isn't very enlightening.. basically all it says is that it wasn't done reading when it should be been done. I see a lot of logging calls in the blackmatch code.. is there perhaps a real Failure logged anywhere? Maybe syslog or something?
Immutable directories have almost exactly the same API as mutable directories, but the blackmatch code has not been updated in forever, so I suspect that there's enough bitrot for the minor differences to cause a problem. I'd suspect something in its use of
DirectoryURI
: new code should be using less of that and more ofclient.create_node_from_uri
.We're not going to finish this for v1.6.1, but hopefully for v1.7.0!
I don't want to touch the fuse code until we have the fuse tests being automatically run by a CI (buildbot) server. So this ticket is blocked on #621 "Incorporate fuse tests into buildbot flow"
This FUSE implementation has been removed (#1409).