tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

add comment clarifying that the button-triggered incident report file is often useflu in *addition* to any automatically triggered incident report files 

[Imported from Trac: page HowToReportABug, version 9]
zooko 2013-01-14 07:54:19 +00:00
parent 82411e546d
commit cdd6576fc4
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
HowToReportABug.md

@ -11,4 +11,4 @@ Either [//cgi-bin/mailman/listinfo/tahoe-dev subscribe to tahoe-dev] and send a
If you don't mind taking an extra few minutes of your time to include the log files, then please include them with your bug report. You can find them in the `logs` subdirectory of the Tahoe-LAFS base directory. The log file named `twistd.log` might be useful, and any log files which are located in the `logs/incidents` subdirectory and which have timestamps around the time of the problem might be useful.
It is also helpful if you go to the "Welcome Page" of your Tahoe-LAFS WUI and scroll to the bottom, where there is a button, labelled "Report an Incident". If you push that button, the gateway will write out a new incident report file into the `logs/incidents` directory.
It is also helpful if you go to the "Welcome Page" of your Tahoe-LAFS WUI and scroll to the bottom, where there is a button, labelled "Report an Incident". If you push that button, the gateway will write out a new incident report file into the `logs/incidents` directory. Please include that one along with any other incident report files that you find in that directory.