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
wonderfly opened this issue
Jan 9, 2015
· 1 comment
Assignees
Labels
🚨This issue needs some love.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
Version of google-http-java-client (e.g. 1.5.0-beta)? http://javadoc.google-http-java-client.googlecode.com/hg/1.10.0-beta/com/google/api/client/http/ExponentialBackOffPolicy.html Java environment (e.g. Java 6, Android 2.3, App Engine)? All Describe the problem. getNextBackOffMillis() almost always returns BackOffPolicy.STOP. That's because getElapsedTimeMillis() is off by a factory of a thousand. For example, after a second of waiting, when I call getElapsedTimeMillis() I get 1000111. How would you expect it to be fixed? getElapsedTimeMillis() needs to divide by 1000.
🚨This issue needs some love.triage meI really want to be triaged.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
From yan...@google.com on June 08, 2012 07:15:09
Version of google-http-java-client (e.g. 1.5.0-beta)? http://javadoc.google-http-java-client.googlecode.com/hg/1.10.0-beta/com/google/api/client/http/ExponentialBackOffPolicy.html Java environment (e.g. Java 6, Android 2.3, App Engine)? All Describe the problem. getNextBackOffMillis() almost always returns BackOffPolicy.STOP. That's because getElapsedTimeMillis() is off by a factory of a thousand. For example, after a second of waiting, when I call getElapsedTimeMillis() I get 1000111. How would you expect it to be fixed? getElapsedTimeMillis() needs to divide by 1000.
Original issue: http://code.google.com/p/google-http-java-client/issues/detail?id=126
The text was updated successfully, but these errors were encountered: