Skip to content

Fix Rich markup error in PortScan prompt - #698

Open
LeVarez wants to merge 1 commit into
Z4nzu:masterfrom
LeVarez:fix/port-scan-markup-error
Open

Fix Rich markup error in PortScan prompt#698
LeVarez wants to merge 1 commit into
Z4nzu:masterfrom
LeVarez:fix/port-scan-markup-error

Conversation

@LeVarez

@LeVarez LeVarez commented May 5, 2026

Copy link
Copy Markdown

Summary

  • Fixed mismatched Rich markup tags in PortScan.run() that caused a MarkupError at runtime
  • Opening tag [bold] didn't match closing tag [/bold magenta] — updated to [bold magenta]...[/bold magenta]

Test plan

  • Run the tool and select "Port Scanning" — the prompt should display without crashing

🤖 Generated with Claude Code

The closing tag `[/bold magenta]` did not match the opening tag `[bold]`,
causing a MarkupError at runtime. Updated the opening tag to `[bold magenta]`
so both tags match.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@jaclinger

Copy link
Copy Markdown

I’m still learning this project, but I think this approach makes the code easier to follow. Nice improvement.

@LeVarez

LeVarez commented May 7, 2026

Copy link
Copy Markdown
Author

I’m still learning this project, but I think this approach makes the code easier to follow. Nice improvement.

I was testing the app and noticed that these kinds of errors were also happening in other tools. I think it would make sense to create a list and double-check all of them. As additional information, I was testing it on macOS.

@sukrammunda64833-spec

Copy link
Copy Markdown
1778843651540 Iska ditell

@sukrammunda64833-spec

Copy link
Copy Markdown

I was testing the app and noticed that these kinds of errors were also happening in other tools. I think it would make sense to create a list and double-check all of them. As additional information, I was testing it on macOS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants