Ping failure console.log's and interrupts clack output

[rvagg]

  ◑  Uploading to FilecoinProvider 0xB709A785c765d7d3F7d94dbA367DA6a611D7972b (ID: 5) failed ping: Ping failed
  ◇  ✓ [Primary] Stored on provider 9
  │
  ◇  ✓ [Secondary] Stored on provider 4
  │
  ◇  ✓ [Secondary] Piece added to Data Set (unconfirmed on-chain)

I think this is just a matter of converting the error to an info log or a spinner msg in that position. This regularly fails for me so probably easy for me to fix it, my wallet wants to keep going back to provider 5 who can't be contacted atm.

[SgtPooki]

2026-06-16

Root cause is upstream. During provider selection in executeUpload, synapse-sdk pings each candidate and, on failure, logs with a raw console.warn before excluding the provider:

@filoz/synapse-sdk packages/synapse-sdk/src/storage/context.ts:610-617:

} catch (error) {
  console.warn(
    `Provider ${candidate.provider.serviceProvider} (ID: ${candidate.provider.id}) failed ping:`,
    error instanceof Error ? error.message : String(error)
  )
  excludeProviderIds.push(candidate.provider.id)
  pingFailures++
}

That console.warn writes straight to stderr mid-render, which is what punches through the clack spinner. Nothing in filecoin-pin emits it, so the fix belongs in synapse-sdk: route the ping failure through the SDK's logger, or surface it as a provider-selection progress event the caller can render. A local console-intercept workaround here is not the path we want.

Filed upstream as FilOzone/synapse-sdk#850. This issue tracks the SDK fix landing here.