You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both baseToken.WaitTimeout and baseToken.setError acquire the lock before proceeding. It results in that baseToken.WaitTimeout can not return earlier even if the operation has failed with an error. Is it by design or a logic flaw?
The text was updated successfully, but these errors were encountered:
Well spotted; it looks like the mutex lock was adeded ages ago when the WaitTimeout function accessed a struct variable (.ready). As it only accesses the channel now I have submitted pull request #383 to remove the lock (and add a test that demonstrates that this fixes the issue)
Both baseToken.WaitTimeout and baseToken.setError acquire the lock before proceeding. It results in that baseToken.WaitTimeout can not return earlier even if the operation has failed with an error. Is it by design or a logic flaw?
The text was updated successfully, but these errors were encountered: