chifra manifest --pins

[tjayrush]

If this thing fails, it reports the failure to the screen which, of course, gets lost unless we capture it.

This makes running the pinning session impossible unless one is watching it.

[tjayrush]

After the round is done, it does report errors, but it only shows the errors from the pinning provider. It does not enhnace those errors with the block range that failed.

For example, this problem:

INFO[05-06|14:02:04.987] Pinned 019889601-019892133 local to  QmXMfvsq2ct8Yy2NaFnJhfnYJDC4HP37ei1u5TyW14yVcx QmaRrMPtmFb36mhkFvH3Ls82vkowihUzKo9GsGXdNf4MQu
EROR[05-06|14:02:34.985] Pin failed: /Users/jrush/Data/trueblocks/v1.0.0/unchained/mainnet/blooms/019889601-019892133.bloom Post "https://api.pinata.cloud/pinning/pinFileToIPFS": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
WARN[05-06|14:02:34.987] Pins mismatch: QmXMfvsq2ct8Yy2NaFnJhfnYJDC4HP37ei1u5TyW14yVcx   QmXMfvsq2ct8Yy2NaFnJhfnYJDC4HP37ei1u5TyW14yVcx
WARN[05-06|14:02:35.009] Pins mismatch: QmaRrMPtmFb36mhkFvH3Ls82vkowihUzKo9GsGXdNf4MQu   QmaRrMPtmFb36mhkFvH3Ls82vkowihUzKo9GsGXdNf4MQu

Produces this error:

Post \"https://api.pinata.cloud/pinning/pinFileToIPFS\": context deadline exceeded (Client.Timeout exceeded while awaiting headers

Not enough to recover.