Errors and Consistency in Server Config / Health
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 440
- Forks
- 48
- Avg merge
- 28m
- Merged PRs (30d)
- 1
Description
This is for 8fd8590dd6e4330f65f4bd8a5f2dcab0ca525ef9
The dialogue under `Tools -> Health Check` yields correct server health status:
However, the dialogue under `Tools -> Server Configuration -> Test Connections` doesn't yield the same results and one of the outputs are duplicated:
This UI should also be updated to reflect depending on which ghidra interface is being used (GhidraMCP or PyGhidra). Right now it looks like it is only setup for GhidraMCP.
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 at commit 8fd8590dd6e4330f65f4bd8a5f2dcab0ca525ef and trace the Tools → Health Check and Tools → Server Configuration → Test Connections entry points. Compare their displayed health results and duplicated output, then inspect how the UI identifies GhidraMCP versus PyGhidra. Done means both dialogs present consistent, non-duplicated results and interface-specific configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100