| Fatal error gate on launch |
The bxp-gui-bridge library is missing from the bundle, or it returned no parseable docs catalog. Both are fatal — the editor never opens. Reinstall the desktop package. |
dry-run / full-run greyed out |
No config is open, the other run mode is already streaming, or a cancel is still in flight. A template does not need to be selected — an empty selection runs every template. |
| SAVE / undo / redo greyed out |
The config was loaded with errors, which latches the editor read-only for the session. Fix the file on disk and reload (ctrl+r). SAVE alone also greys out while any live validation error is attached. |
cancel sits on cancelling… |
Cancel signals the bxp-cli child once (SIGTERM / TerminateProcess) and then waits for it to exit — there is no forced kill and no idle watchdog. Whatever streamed before the signal stays visible. |
A cancelled full-run left a short .csvx |
Expected. Output is written as the run proceeds, so a run stopped part-way leaves the rows it had already produced. Delete the file before re-running, or re-run without --fresh so it is rebuilt rather than skipped. |
| Slow load on a network-mounted config |
Load and save validation include filesystem-existence checks with a 2-second deadline. On the first [fs.timeout] warning the GUI drops the check for the rest of the session — Settings inspector → Config → fsCheckSlow then reads true. |
Tree shows $err_<N> / $warn_<N> keys |
Expected, not a bug: those are the validation markers the bridge attaches next to the offending entry. The tree paints them as chips rather than as literal keys; seeing the raw key means you are looking at exported JSON, not the editor. |