9ad3afbd22
- Updated Definition of Done report with detailed checks and results for backend and frontend tests. - Documented issues related to race conditions and test failures in QA reports. - Improved security scan notes and code cleanup status in QA reports. - Added summaries for rate limit integration test fixes, including root causes and resolutions. - Introduced new debug and integration scripts for rate limit testing. - Updated security documentation to reflect changes in configuration and troubleshooting steps. - Enhanced troubleshooting guides for CrowdSec and Go language server (gopls) errors. - Improved frontend and scripts README files for clarity and usage instructions.
13 lines
604 B
Markdown
13 lines
604 B
Markdown
# Troubleshooting gopls / VS Code Go errors in Charon
|
|
|
|
This page documents how to triage and collect logs for persistent Go errors shown by gopls or VS Code in the Charon repository.
|
|
|
|
Steps:
|
|
|
|
1. Open the Charon workspace in VS Code (project root).
|
|
2. Accept the workspace settings prompt to apply .vscode/settings.json.
|
|
3. Run the workspace task: Go: Build Backend (or run ./scripts/check_go_build.sh).
|
|
4. If errors persist, run ./scripts/gopls_collect.sh and attach the output directory to an issue.
|
|
|
|
When filing upstream issues, include gopls.log, go-version.txt, go-env.txt, and a short reproduction.
|