I'll note that after the fetch fails, it leaves the master branch in a write-locked state.
So it is possible that the ConcurrentRequest issues is just because we are getting a different exception while streaming. And that the code to unlock is the bit responsible for the TooManyRequests failure, and it is masking the real failure.
I'll note that after the fetch fails, it leaves the master branch in a write-locked state.
So it is possible that the ConcurrentRequest issues is just because we are getting a different exception while streaming. And that the code to unlock is the bit responsible for the TooManyRequests failure, and it is masking the real failure.