vibe-validate 0.17.0 → 0.17.1-rc.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,65 @@
1
+ # Troubleshooting vibe-validate
2
+
3
+ ## Common Issues
4
+
5
+ ### Cache Not Working
6
+
7
+ **Symptom:** Validation always runs, even when code hasn't changed
8
+
9
+ **Diagnose:**
10
+ ```bash
11
+ # Check if git is available
12
+ git --version
13
+
14
+ # Check current tree hash
15
+ git write-tree
16
+
17
+ # Check vibe-validate state
18
+ vv state
19
+ ```
20
+
21
+ **Solutions:**
22
+ 1. **Ensure working in a git repository**
23
+ ```bash
24
+ git status # Should work
25
+ ```
26
+
27
+ 2. **Check for uncommitted changes**
28
+ ```bash
29
+ git status # Should be clean for cache to work
30
+ ```
31
+
32
+ 3. **Force cache refresh**
33
+ ```bash
34
+ vv run --force <command>
35
+ ```
36
+
37
+ ### Errors Not Being Extracted
38
+
39
+ **Symptom:** `exitCode !== 0` but `totalErrors === 0`
40
+
41
+ **Diagnose:**
42
+ ```bash
43
+ # Check what extractor was used
44
+ vv run <command>
45
+ # Look for: metadata.detection.extractor
46
+
47
+ # If "generic" → need custom extractor
48
+ ```
49
+
50
+ **Solution:** Create custom extractor (see `resources/extending-extraction.md`)
51
+
52
+ ### Command Always Fails
53
+
54
+ **Symptom:** Same command works without `vv run` but fails with it
55
+
56
+ **Possible causes:**
57
+ 1. Command requires interactive input (not supported)
58
+ 2. Command uses TTY detection
59
+ 3. Command has side effects that fail in isolated execution
60
+
61
+ **Solution:** Run without vibe-validate for interactive commands
62
+
63
+ ## Complete Troubleshooting Guide
64
+
65
+ See: `docs/troubleshooting.md` in the main documentation