af8384046c
- Replace Go interface{} with any (Go 1.18+ standard)
- Add database indexes to frequently queried model fields
- Add JSDoc documentation to frontend API client methods
- Remove deprecated docker-compose version keys
- Add concurrency groups to all 25 GitHub Actions workflows
- Add YAML front matter and fix H1→H2 headings in docs
Coverage: Backend 85.5%, Frontend 87.73%
Security: No vulnerabilities detected
Refs: docs/plans/instruction_compliance_spec.md
18 lines
784 B
Markdown
18 lines
784 B
Markdown
---
|
|
title: Troubleshooting gopls / VS Code Go Errors
|
|
description: Resolve gopls and VS Code Go extension errors in the Charon repository. Log collection and common fixes.
|
|
---
|
|
|
|
## 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.
|