getappmap / getappmap/appmap-js
Scanner errors when AppMap does not exist
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
[stderr] yarn run scanner scan --watch --appmap-dir .: node:internal/process/promises:279
triggerUncaughtException(err, true /* fromPromise */);
^[Error: ENOENT: no such file or directory, open 'api/tmp/appmap/rspec/Spree_Api_PromotionsController_GET_show_when_admin_when_finding_by_id_behaves_like_a_JSON_response_should_be_ok.appmap.json'] {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: 'api/tmp/appmap/rspec/Spree_Api_PromotionsController_GET_show_when_admin_when_finding_by_id_behaves_like_a_JSON_response_should_be_ok.appmap.json'
}
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
Start by reproducing the failure with yarn run scanner scan --watch --appmap-dir . and inspect how the scanner handles the missing path shown in the ENOENT stack trace. Done should mean scanning does not crash when the referenced AppMap file is absent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100