Reporting Bugs

Reporting bugs

Two ways in:

• A GitHub issue, preferred: others can find and follow it.
• Email wfweb@k1fm.us if you have no GitHub account. Logs and screenshots as attachments are welcome.

Questions and "is this expected?" go to Discussions.

What to include

• Build and version: Server or Standalone; the version from wfweb --version, the release filename, or the page's footer.

• Rig and connection: model, USB or LAN, and for USB whether it is the radio's own port or an interface such as a Digirig.

• Where the server runs (OS, Pi or PC, Docker) and which browser on which device opens the page.

• The log. Run the server with debug logging to a file, reproduce, attach the file:

  wfweb --debug /tmp/wfweb-debug.log

  It has the CI-V traffic, the power and VFO decisions and the cache updates, which is usually enough to see what the radio answered. In Docker, docker logs has the plain log; add --debug to the run command for the verbose one.

• The browser console for anything on the page: F12 › Console, copy what is red. Audio problems print [Audio] lines there.

• What you expected and what happened, with the steps. A screenshot of the page, or a recording from the REC button, often says it faster.

What is useful to know before filing

• The Troubleshooting and FAQ page lists the known ones with their fixes.
• Many "wfweb does X wrong" reports are a radio menu: see Icom Menu Settings.
• Rig-specific behaviour (a command the radio refuses, a layout that differs) goes in the rig file under rigs/; a report that quotes the CI-V frame from the debug log and the page of the radio's CI-V reference manual is the fastest path to a fix.