[
https://issues.apache.org/jira/browse/CAMEL-25426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-25426:
--------------------------------
Description:
An umbrella for small bugs and usability issues found while going through every
screen of the camel-jbang monitor with all 40 built-in examples, before the
4.23.0 release. Fixed in a few PRs grouped by area, one commit per fix:
* the lifecycle of runs: an infra example dropped after 120 s while its
container still starts, a failed infra start not shown, a failed run reported
as started, an opened Maven project left as Starting after a failed run, a
failed dev-mode reload not shown on the Overview or after a save in the editor
* the MCP tools: stale Overview rows from tui_get_table while another tab is
active, tabs missing from tui_get_options
* tables and layout: rows hidden after the list shrinks, text cut without an
ellipsis, the column that names the thing squeezed first (Overview NAME at 100
columns, Inspect PROCESSOR, Errors MESSAGE, Routes TOTAL)
* small usability: the shell rejects a leading camel, undo leaves the file
marked changed, convert leaves duplicate routes, Inspect step times out of
order, the Architecture Flow panel covering a box, the AI Log detail not
wrapping, Process tab without help, emoji alignment in menus, and similar
* the example catalog: cloud/aws-sqs asks for infra aws instead of aws sqs
* docs: screenshots for the pages that have none, and the settings page brought
up to date
was:
An umbrella for small bugs and usability issues found while going through every
screen of the camel-jbang monitor (camel tui) with all 40 built-in examples,
before the 4.23.0 release. Fixed in a few PRs grouped by area, one commit per
fix:
* the lifecycle of runs: an infra example dropped after 120 s while its
container still starts, a failed infra start not shown, a failed run reported
as started, an opened Maven project left as Starting after a failed run, a
failed dev-mode reload not shown on the Overview or after a save in the editor
* the MCP tools: stale Overview rows from tui_get_table while another tab is
active, tabs missing from tui_get_options
* tables and layout: rows hidden after the list shrinks, text cut without an
ellipsis, the column that names the thing squeezed first (Overview NAME at 100
columns, Inspect PROCESSOR, Errors MESSAGE, Routes TOTAL)
* small usability: the shell rejects a leading camel, undo leaves the file
marked changed, convert leaves duplicate routes, Inspect step times out of
order, the Architecture Flow panel covering a box, the AI Log detail not
wrapping, Process tab without help, emoji alignment in menus, and similar
* the example catalog: cloud/aws-sqs asks for infra aws instead of aws sqs
* docs: screenshots for the pages that have none, and the settings page brought
up to date
> camel-jbang - Minor bugs and usability fixes in the monitor before 4.23
> -----------------------------------------------------------------------
>
> Key: CAMEL-25426
> URL: https://issues.apache.org/jira/browse/CAMEL-25426
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 4.23.0
>
>
> An umbrella for small bugs and usability issues found while going through
> every screen of the camel-jbang monitor with all 40 built-in examples, before
> the 4.23.0 release. Fixed in a few PRs grouped by area, one commit per fix:
> * the lifecycle of runs: an infra example dropped after 120 s while its
> container still starts, a failed infra start not shown, a failed run reported
> as started, an opened Maven project left as Starting after a failed run, a
> failed dev-mode reload not shown on the Overview or after a save in the editor
> * the MCP tools: stale Overview rows from tui_get_table while another tab is
> active, tabs missing from tui_get_options
> * tables and layout: rows hidden after the list shrinks, text cut without an
> ellipsis, the column that names the thing squeezed first (Overview NAME at
> 100 columns, Inspect PROCESSOR, Errors MESSAGE, Routes TOTAL)
> * small usability: the shell rejects a leading camel, undo leaves the file
> marked changed, convert leaves duplicate routes, Inspect step times out of
> order, the Architecture Flow panel covering a box, the AI Log detail not
> wrapping, Process tab without help, emoji alignment in menus, and similar
> * the example catalog: cloud/aws-sqs asks for infra aws instead of aws sqs
> * docs: screenshots for the pages that have none, and the settings page
> brought up to date
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
