… will be 3 on a failed refresh by returning bad tokens on subsequent calls
Initially I thought I had implemented the flow wrongly because I did in go, but it was only the test that was wrong thankfully. To be fair, I think the test changed in the spec to mention returning a bad token on subsequent callback calls in order to get a callback count of 3 (fails due to failpoint, fails due to refresh, fails due to attempt to do access token with bad token).
… will be 3 on a failed refresh by returning bad tokens on subsequent calls
Initially I thought I had implemented the flow wrongly because I did in go, but it was only the test that was wrong thankfully. To be fair, I think the test changed in the spec to mention returning a bad token on subsequent callback calls in order to get a callback count of 3 (fails due to failpoint, fails due to refresh, fails due to attempt to do access token with bad token).