getappmap / getappmap/appmap-js
`Error: EISDIR: illegal operation on a directory, watch '.'` in indexer
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
Stderr: node:internal/errors:464
ErrorCaptureStackTrace(err);
^
Error: EISDIR: illegal operation on a directory, watch '.'
at FSWatcher.<computed> (node:internal/fs/watchers:244:19)
at Object.watch (node:fs:2251:34)
at createFsWatchInstance (c:\Users\TEST\AppData\Roaming\Code\User\globalStorage\appland.appmap\node_modules\chokidar\lib\nodefs-handler.js:119:15)
at setFsWatchListener (c:\Users\TEST\AppData\Roaming\Code\User\globalStorage\appland.appmap\node_modules\chokidar\lib\nodefs-handler.js:166:15)
at NodeFsHandler._watchWithNodeFs (c:\Users\TEST\AppData\Roaming\Code\User\globalStorage\appland.appmap\node_modules\chokidar\lib\nodefs-handler.js:331:14)
at NodeFsHandler._handleDir (c:\Users\TEST\AppData\Roaming\Code\User\globalStorage\appland.appmap\node_modules\chokidar\lib\nodefs-handler.js:567:19)
at NodeFsHandler._addToNodeFs (c:\Users\TEST\AppData\Roaming\Code\User\globalStorage\appland.appmap\node_modules\chokidar\lib\nodefs-handler.js:617:27)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
at async c:\Users\TEST\AppData\Roaming\Code\User\globalStorage\appland.appmap\node_modules\chokidar\index.js:451:21
at async Promise.all (index 0) {
errno: -4068,
syscall: 'watch',
code: 'EISDIR',
path: '.',
filename: '.'
}
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report identifies the indexer and a chokidar/Node fs.watch stack trace; begin by reproducing the Windows failure and locating the indexer watch setup. The issue does not name a source file, test, or expected behavior, so completion criteria must be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100