|
Some checks failed
Security / Security check (push) Failing after 1s
Studio defaulted its endpoint to the local channel's port (:50051), but
a curl|sh user is on the production channel (:50071) — so the sidebar
probed a different daemon than the Diagnose page reported, showing
'connected' next to 'production daemon stopped'. On first run Studio now
reads ~/.chain/current-channel (+ run/<ch>.endpoint) and follows the
active channel; an explicit Settings endpoint still wins and persists,
auto-discovery does not (re-follows the channel each launch). The
connection caption now names the channel ('Connected · production') so
it can never look contradictory again.
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 | ||