The "Report!" button in the "Report an Incident" form field redirects to a misleading/incomplete message #1706
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#1706
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 "report_incident" page that is served as a redirection should say:
"Thank you for your report! It was stored as .flog.bz2 in /logs/incidents. This node has/has not registered with an incident gatherer."
If it has:
"Incident gatherer :"
#1974 was mostly a duplicate of this, and was fixed in 30924a506ced5c1f06e034b4f1482217746255ca but I didn't see this ticket until now so I didn't implement the incident gatherer part and I didn't include the filename of the report in the message.
Hopefully an incident report is actually saved to disk even if an incident gatherer is configured? If not, the current message is still incorrect/misleading in the case that an incident gatherer is configured (it says "An incident report has been saved to logs/incidents/ in the node directory").
Incident reports are always written to disk. The gatherer is secondary/supplemental.
We probably don't want to reveal too much about the incident gatherer (like it's IP address), other than it's existence, from the unauthenticated welcome page. Unfortunately I don't think we have a useful "name" for the gatherer anywhere.