getappmap / getappmap/appmap-js
Large sequence diagram is omitted from the Navie context
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
I have this AppMap data file in my project:
org_finos_waltz_integration_test_inmem_service_PhysicalFlowServiceTest_create_PhysicalFlowUsesDefaultExternalIdIfNotSpecified.appmap.json
When I ask Navie a question, it sees the file, but doesn't add it to the context.
Logging in AppMap: Services Output view when DEBUG=true:
56633 [Stdout] Remaining characters before context: 15741
56633 [Stdout] Skipping context item sequence-diagram /Users/ajp/src/finos/waltz/tmp/appmap/junit/org_finos_waltz_integration_test_inmem_service_PhysicalFlowServiceTest_create_PhysicalFlowUsesDefaultExternalIdIfNotSpecified.appmap.json due to size. 7521 > 3148.2
56633 [Stdout] Context item sequence-diagram /Users/ajp/src/finos/waltz/tmp/appmap/junit/org_finos_waltz_integration_test_inmem_service_PhysicalFlowServiceTest_create_PhysicalFlowUsesDefaultExternalIdIfNotSpecified.appmap.json status: item_too_big
- Ensure that at least one sequence diagram is allowed in the context, regardless of the token limit.
- Ensure that at least 5 code snippets are allowed in the context as well.
- Accomplish this behavior by overriding the token limit, rather than trying to predict or recalculate the token limit based on the content size.
- Note that no changes are needed for the frontend / UI to solve this issue.
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 tracing the context-item size filtering that produces the item_too_big message in the AppMap: Services output. Verify that at least one sequence diagram and five code snippets remain in context despite the token limit, without changing the frontend/UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ai, developer-experience
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100