Clicking "To view the global shared filestore, Click Here!" in client attached to Test Grid raises AssertionError #95
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#95
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?
eek, that's formatted pretty badly.. maybe you could add the traceback as an attachment instead?
Is it possible that you have a node that was initialized before the switch-to-zbase32 change that occurred on july-24, but is now running with new code?
The dirnode URI format changed (and testnet was flushed), so you need to at least remove the global_root.uri and my_vdrive.uri files from it. You may want to delete the whole node and create a brand new one.
If you make a new node and look at those files, check to see if the URIs look different between your old one and the new one. The old ones would have lots of trailing === marks, the new ones should have no equal marks.
If we can confirm that this is the problem, could you close this ticket?
thanks,
-Brian
Also changeset:dbcabc114234cfe5 made it so that this kind of incompatibility will be handled nicely explicitly from now on. arch: please close this ticket if you agree that the issue is fixed.