Add multi-host boot consistency smoke test for installed agents
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- api, cli, testing-qa
Research direction
Start with the smoke/integration harness and the shell, agentServer, and web API host entry points. Create a fresh instance directory containing agents.json and the install-source configuration, then boot all three paths against it. Done means every host reports the same installed agents and source-derived state, with restart/reload coverage if the harness supports it cheaply.
Written by the indexing model from the issue text.
Description
Summary
Add a smoke/integration scenario that boots the shell, agentServer, and web API host paths against one fresh instance directory and verifies they observe the same installed-agent state.
Background
The per-host wiring is covered by build/type-check and unit tests around the shared installed-agent records, but no single test boots all host entry points against the same agents.json / install-source config and verifies consistent visibility.
Suggested Coverage
- create a fresh instance directory with installed-agent state
- boot shell, agentServer, and API host paths against that instance directory
- verify all hosts see the same installed agents and source-derived state
- include restart/reload behavior if the smoke harness can do so cheaply
Source
Deferred from PR #2611 review-log cleanup.
- Dominant language
- TypeScript
- Stars
- 744
- Forks
- 107
- Avg merge
- 1d 59m
- Merged PRs (30d)
- 113
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from microsoft/TypeAgent
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Add CI validation for schema keyword driftMay be free again @GeorgeNgMsft claimed this 32 days ago, and no pull request is open. Open
microsoft/TypeAgent#2978 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
dispatcher enhancement security
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
All issues in microsoft/TypeAgent
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Small-tailqwq/dsh-deep-whale#187 ·
Maintainers usually reply within 1 day
-
Tela Marca manda conferir o campo "Razão social", que em Portugal se chama "Denominação social"Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
melgarafael/DeskcommCRM#2503 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
0x80/isolate-package#218 ·
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pingdotgg/t3code#16859 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day