From 85d390b43f805a8117ab70fbeca526c7aa7e4df0 Mon Sep 17 00:00:00 2001 From: DaneEvans Date: Tue, 5 Aug 2025 21:56:10 +1000 Subject: [PATCH] add howto get logs (#2637) --- .github/ISSUE_TEMPLATE/bug_report.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index d60b94950..ca72e5141 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -58,12 +58,39 @@ body: placeholder: 2.4.1.394e0e1 Beta validations: required: true + + - type: markdown + attributes: + value: | + Logs help us to diagnose and reproduce issues, particularly when they are unique to your setup. + Depending on the issue, the following logs may be useful: + - App logs: This will help with most issues. + - Use logcat (with Android studio is simplest) and filter by com.geeksville.mesh + - Mesh logs: UI issues, communication issues etc. + - ` App > Menu > Debug Panel > Export specific / export all ` + - Android logs: Potentially useful if the issue goes beyond the app (connections, network etc.) + - Use logcat (with Android studio is simplest) and figure out what filters are needed to show us what is going wrong. + - Firmware logs: Useful for all connection issues with nodes + - These are piped to the USB serial port on the node, the most foolproof is to use the 'open serial' button on the web-flasher interface, and then save the output. + - You need to be connecting to the node via Bluetooth or Network for this to work. + - type: markdown + attributes: + value: | + + ### Relevant log output +
+ + Expand Logs ... - type: textarea id: logs attributes: label: Relevant log output description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks. render: shell + - type: markdown + attributes: + value: | +
- type: checkboxes id: terms attributes: