You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix ENOBUFS error during GitHub issues/PRs indexing for large repositories
8
+
9
+
**Problem:** When indexing repositories with many GitHub issues/PRs (especially with large issue bodies), the `dev index` command would fail with `ENOBUFS` (No buffer space available) error.
10
+
11
+
**Solution:**
12
+
- Increased execSync maxBuffer from default 1MB to 50MB for issue/PR fetching
13
+
- Reduced default fetch limit from 1000 to 500 items to prevent buffer overflow
14
+
- Added `--gh-limit` CLI flag to allow users to customize the limit
15
+
- Improved error messages to guide users when buffer issues occur
16
+
17
+
**Changes:**
18
+
-`fetchIssues()` and `fetchPullRequests()` now use 50MB maxBuffer
19
+
- Default limit changed from 1000 to 500 (per type: issues and PRs)
20
+
- Added `--gh-limit <number>` flag to `dev index` command
21
+
- Better error handling with helpful suggestions (use `--gh-limit 100` for very large repos)
22
+
- Comprehensive test coverage (23 new tests for fetcher utilities)
23
+
24
+
**Usage:**
25
+
```bash
26
+
# Default (works for most repos)
27
+
dev index
28
+
29
+
# For large repos (200+ issues/PRs)
30
+
dev index --gh-limit 200
31
+
32
+
# For very active repos (500+ issues/PRs)
33
+
dev index --gh-limit 100
34
+
```
35
+
36
+
**Testing:** All 1100+ tests passing. Verified on lytics-ui repository (6989 files, 1000 issues/PRs indexed successfully).
0 commit comments