• start off with client not aware that there's an update to pull on remote
  I know there is one, because someone in my team just pushed an update
• I click the pull button anyway
• what seems to happen in the background is that ST is refreshing remote status
• the pull fails because of a lock problem (probably created by the refresh)
• I have to 'ack' the error, and then pull again - which works now that there's no refresh happening.

I would prefer that:
a. either the pull would wait in the refresh to finish
b. OR it would just retry / override the problem and pull

Thanks
Dan