|
Some checks failed
Security / Security check (push) Failing after 2s
'Tap to start' on an already-running hub reported 'daemon could not be started' (the start failed because it was already up) then flashed the error away as a SnackBar — confusing next to the sidebar's 'connected'. Now: on a failed start, probe the hub; if it answers, just connect (no false error). If it is genuinely down, show the daemon's stderr in a persistent, copyable dialog (showFaiProcessErrorDialog) instead of a SnackBar that vanishes before the operator can read or copy it. Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com> |
||
|---|---|---|
| .. | ||
| chain_log.dart | ||
| error_presentation.dart | ||
| flow_output.dart | ||
| flow_run_driver.dart | ||
| format.dart | ||
| friendly_error.dart | ||
| hub.dart | ||
| hub_auth_token.dart | ||
| registry_token.dart | ||
| system_actions.dart | ||
| theme_plugin.dart | ||
| today_story_loader.dart | ||