getappmap / getappmap/appmap-js

Navie hangs after context search completes

Open
#2,241 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
53
Forks
18
Avg merge
3d 18h
Merged PRs (30d)
8

Description

Navie responses sometimes appear to hang indefinitely until a timeout occurs, ultimately displaying the error message:

No search request with id: <uuid>

Subsequent prompts (such as next steps) do appear to resolve correctly.


Environment:

Operating System: Windows 11
IDE: JetBrains
AppMap Plugin for JetBrains: v0.77.0
AppMap CLI: v3.185.2
OpenAI Model: GPT-4o (August)
Network: Corporate proxy configured


Steps to Reproduce:

  1. Pin a text file in the IDE.
  2. Issue the prompt: @plan.
  3. Observe the context:
    • The pinned file is successfully included.
    • Sequence diagrams and code snippets appear, indicating that indexing, vector terms, context search, etc. are working.
  4. Notice the behavior:
    • The text cursor blinks for several minutes until the request times out.
    • Navie then displays the error: No search request with id: <uuid>.
  5. Follow-up:
    • Subsequent prompts resolve normally.

Expected Behavior:
Navie should return the results for the context search promptly without hanging or timing out.


Actual Behavior:
After the context search completes, Navie hangs (as indicated by a blinking cursor) until it times out, ultimately presenting an error message regarding a missing search request ID.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Reproduce @plan in JetBrains with a pinned text file, then trace the context-search request lifecycle through the TypeScript client; done means the response returns without hanging, timing out, or showing a missing search request ID.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
ai, developer-experience, search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.