There are two race conditions in the campaignProgressPrinter:

1. We found a workaround for the first one here: Fix status bar updates getting lost src-cli#389 (comment) But we should fix it properly.
2. I discovered a second one: campaignProgressPrinter reads and mutates its own state across multiple calls of PrintStatuses. These calls can happen in separate goroutines, which might leak to concurrent accesses of the same data structures (and caused a panic for me locally)