vrr/spawn
2
0
Fork 0
mirror of https://github.com/OpenRouterTeam/spawn.git synced 2026-05-03 06:10:21 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

fix: use log_step (cyan) for in-progress messages instead of log_info (green) (#757)

Browse source 
Consistently use log_step for progress/status messages ("Waiting for...",
"Fetching...", "Creating...") and reserve log_info for success/completion
messages. This gives users a clear visual distinction between operations
that are still running (cyan) vs operations that have completed (green).

Also adds periodic progress updates to silent polling loops in ramnode,
cherry, and netcup IP wait functions so users see activity during long waits.

Agent: ux-engineer

Co-authored-by: A <6723574+louisgv@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
A 2026-02-12 15:48:38 -08:00 • committed by GitHub
parent 32a3e6e276
commit cf53ea1fb2
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
20 changed files with 41 additions and 32 deletions
Download patch file Download diff file Expand all files Collapse all files

4
github-codespaces/lib/common.sh
View file

@ -89,7 +89,7 @@ create_codespace() {
local machine="${2:-basicLinux32gb}"
local idle_timeout="${3:-30m}"
log_info "Creating GitHub Codespace..."
log_step "Creating GitHub Codespace..."
log_info "Repo: $repo"
log_info "Machine: $machine"
log_info "Idle timeout: $idle_timeout"
@ -117,7 +117,7 @@ wait_for_codespace() {
local max_attempts=60
local attempt=0
log_info "Waiting for codespace to be ready..."
log_step "Waiting for codespace to be ready..."
while [[ $attempt -lt $max_attempts ]]; do
local state