[portlandhodl]

Problem

sst tunnel dies when a client opens several connections at once, e.g. a Postgres connection pool through an sst.aws.Vpc bastion:

fatal error: concurrent map read and map write

github.com/charmbracelet/lipgloss.(*Style).set          set.go:30
github.com/charmbracelet/lipgloss.Style.Bold            set.go:36
github.com/sst/sst/v3/pkg/tunnel.StartProxy.func1       pkg/tunnel/proxy.go:32
github.com/armon/go-socks5.(*Server).handleConnect

go-socks5 runs each connection's Dial in its own goroutine, and the proxy logs each one with ui.GetColor(addr).Bold(true). GetColor returns an entry from the global ui.Colors by value, but lipgloss v0.9.1 styles keep their rules in a map that is shared across value copies, so Bold(true) writes into the shared global map. Concurrent connections race on it and the Go runtime kills the process, which drops the tunnel.

Fix

GetColor now returns Colors[i].Copy(), which deep-copies the rules map, so callers can chain setters without touching shared state. proxy.go is the only caller today, but fixing it in GetColor covers any future ones too.

Testing

Added cmd/sst/mosaic/ui/ui_test.go:

• TestGetColorConcurrentUse: 32 goroutines calling GetColor(addr).Bold(true).Render(...)
• TestGetColorDoesNotMutateColors: checks that Colors isn't changed through GetColor

go test -race ./cmd/sst/mosaic/ui/:

• without the fix: the test binary crashes with fatal error: concurrent map read and map write (28 DATA RACE reports)
• with the fix: ok

🤖 Generated with Claude Code