debugging internals,
DWARF format, OS-specific process control, and Go runtime internals.
## Build and Test Commands
### Building
```bash
make build # Build dlv binary
make install # Install dlv to system
make
No other project uses it yet
25k11mo agoReviewMountCreate a free account to mount
user_decrypt,public_decrypt}.rs # one file per flow: checks, counting, output
├── mock.rs, scenarios.rs # test only: scripted connector, YAML scenario runner
└── scenarios/*.yaml # behaviour scenarios, run by the test suite
25k17mo agoReviewMountCreate a free account to mount
/gradlew :app:assembleDebug # build the demo APK
./gradlew clean
```
There is **no test source set** — there are no unit or instrumented tests in either module. Verify changes by compiling and/or
No other project uses it yet
25k8y agoReviewMountCreate a free account to mount
matches a known active incident. Three sources:
- [ci-health-incidents](https://gitlab.com/gitlab-org/quality/analytics/ci-health-incidents/-/issues?state=opened&label_name[]=ci-health%3A%3Aactive) — test file failures, failure categories, uncategorized job failures
- [ci-health-systemic](https://gitlab.com/gitlab-org/quality/analytics/ci-health-systemic/-/issues?state=opened&label_name[]=ci-health%3A%3Aactive) — recurring systemic failures
No other project uses it yet
25k17d agoReviewMountCreate a free account to mount
directly.
### Required Commands
```bash
# All Python operations must use UV
uv run pytest # Run tests
uv run pytest tests/pm_agent/ # Run specific tests
uv pip install package # Install dependencies
No other project uses it yet
24k12mo agoReviewMountCreate a free account to mount
Learn Go with Tests — writing guide
This is Chris James's ("quii") book. When drafting or editing chapter prose, match his voice, not generic technical-writing tone. This file
No other project uses it yet
24k3mo agoReviewMountCreate a free account to mount
Vuex for state management
- **Desktop**: Electron 31.7.3
- **Build**: ESBuild (main process), Vite (renderer process)
- **Testing**: Vitest for unit and integration tests (see `apps/studio/tests/VITEST_MIGRATION.md`); Playwright for e2e. **All new tests must
24k6d agoReviewMountCreate a free account to mount
source files
- Features/ → Individual ~modules to isolate features
js/ → The JavaScript source files
tests/ → A smattering of PHP tests however, most tests are inside their src/Feature directories
```
# Development Workflow
## Setup
No other project uses it yet
24k9mo agoReviewMountCreate a free account to mount
validate # Validate node data in database
npm run dev # build + rebuild + validate
# Testing
npm test # Run all tests (vitest)
npm run test:unit # Unit tests only
npm run test:integration
Steady19 mentions in 2 weeks
No other project uses it yet
23k2mo agoReviewMountCreate a free account to mount
microservice is automatically accessible to AI agents via the Model Context Protocol (MCP).
## Build & Test
```bash
# Run all tests
make test
# Run tests for a specific package
go test ./gateway/mcp
No other project uses it yet
23k4d agoReviewMountCreate a free account to mount
teardown invariants, and Parcel comparison |
| [docs/testing.md](docs/testing.md) | TDD workflow, determinism, real dependencies over mocks, test organization |
| [docs/qa.md](docs/qa.md) | QA evidence bar for pull requests — platform matrix, version drift, performance
23k3mo agoReviewMountCreate a free account to mount
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.