<p>Thanks <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=1449498" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ManfredKarrer">@ManfredKarrer</a> , I saw the 2-minute timeout constant in the source code, however this doesn't match my practical observations, where the timeout message occurs after 60 seconds only (12:16:38 -> 12:17:38 in my log). It might be a different timeout condition.</p>
<p>Agreed that a socket timeout of 2 minutes makes perfect sense, on the other hand, a <em>data transfer completion</em> timeout (which is what seems to be happening here) makes more sense to be a function of the data size.</p>
<p>I use release v0.9.5 in my tests.</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/bisq-network/bisq/issues/2547#issuecomment-476237722">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtqNamAhXnUnZBA7lXw_mxhUEqID_ks5vaOW1gaJpZM4b4HAA">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtouTDHVwbqKIm0MBpmO8BOMUhCaKks5vaOW1gaJpZM4b4HAA.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/bisq-network/bisq","title":"bisq-network/bisq","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/bisq-network/bisq"}},"updates":{"snippets":[{"icon":"PERSON","message":"@agb19 in #2547: Thanks @ManfredKarrer , I saw the 2-minute timeout constant in the source code, however this doesn't match my practical observations, where the timeout message occurs after 60 seconds only (12:16:38 -\u003e 12:17:38 in my log). It might be a different timeout condition. \r\n\r\nAgreed that a socket timeout of 2 minutes makes perfect sense, on the other hand, a *data transfer completion* timeout (which is what seems to be happening here) makes more sense to be a function of the data size. \r\n\r\nI use release v0.9.5 in my tests."}],"action":{"name":"View Issue","url":"https://github.com/bisq-network/bisq/issues/2547#issuecomment-476237722"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/2547#issuecomment-476237722",
"url": "https://github.com/bisq-network/bisq/issues/2547#issuecomment-476237722",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>