<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=1011860" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/simonpoole">@simonpoole</a> : I'm a bit curious as to what's your experience with OkHttp in Vespucci - which as we all know is about to be replaced in the near future due to their bold move to Kotlin.</p>
<p>I found a blog post explicitly mentioning retries of HTTP POSTs  "on slow and unreliable connections", see <a href="https://medium.com/inloopx/okhttp-is-quietly-retrying-requests-is-your-api-ready-19489ef35ace" rel="nofollow">https://medium.com/inloopx/okhttp-is-quietly-retrying-requests-is-your-api-ready-19489ef35ace</a> (with section "Fix the real problem" looking very familiar). Some subsequent pull request and issues seemed to have proposed some changes to is, and I'm not exactly sure if that blog post is still accurate as is.</p>
<p>Some people on Stack Overflow recommended to set <code>retryOnConnectionFailure=false</code>, or have some custom interceptor in place. I couldn't find either one by briefly skimming through the Vespucci sources.</p>
<p>Do you have anything special in place to deal with this situation? I would assume poor network connectivity isn't entirely theoretical in places where people use Vespucci.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/issues/2201#issuecomment-485155750">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLJDBTEKKLZK74RZMNLPRNVPRANCNFSM4HEAKOPQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AAK2OLJHM2EO73KGAJK7ZODPRNVPRANCNFSM4HEAKOPQ.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/openstreetmap/openstreetmap-website","title":"openstreetmap/openstreetmap-website","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/openstreetmap/openstreetmap-website"}},"updates":{"snippets":[{"icon":"PERSON","message":"@mmd-osm in #2201: @simonpoole : I'm a bit curious as to what's your experience with OkHttp in Vespucci - which as we all know is about to be replaced in the near future due to their bold move to Kotlin.\r\n\r\nI found a blog post explicitly mentioning retries of HTTP POSTs  \"on slow and unreliable connections\", see https://medium.com/inloopx/okhttp-is-quietly-retrying-requests-is-your-api-ready-19489ef35ace (with section \"Fix the real problem\" looking very familiar). Some subsequent pull request and issues seemed to have proposed some changes to is, and I'm not exactly sure if that blog post is still accurate as is.\r\n\r\nSome people on Stack Overflow recommended to set `retryOnConnectionFailure=false`, or have some custom interceptor in place. I couldn't find either one by briefly skimming through the Vespucci sources. \r\n\r\nDo you have anything special in place to deal with this situation? I would assume poor network connectivity isn't entirely theoretical in places where people use Vespucci."}],"action":{"name":"View Issue","url":"https://github.com/openstreetmap/openstreetmap-website/issues/2201#issuecomment-485155750"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/2201#issuecomment-485155750",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/2201#issuecomment-485155750",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>