getappmap / getappmap/appmap-js
bug: Navie process hangs during index search
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
The index search is synchronous and unyielding, so computationally expensive lookups cause the process to hang. This is particularly noticeable when a large number of search terms are used, such as during @review.
An easy way to replicate this would be to request @review, then open a new Navie tab. The second tab will be stuck in a loading state until the first context search completes.
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 synchronous index search with an @review request, then open a new Navie tab and trace the Navie process while the first context search runs. Done means the second tab does not remain stuck loading while the first search completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100