<p></p>
<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/cbeams/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/cbeams">@cbeams</a>,</p>
<p>I will see the keybase video later today.  But today I reproduced the error (once) and am working on it now.</p>
<p>An interval of tor circuit breakdown during startup prevented the wallet balance from being updated.<br>
When I see a series of tor debug statements like these:</p>
<pre><code>CircuitStatus: 92 CLOSED
CircuitStatus: 92 CLOSED
CircuitStatus: 144 FAILED
CircuitStatus: 148 LAUNCHED
CircuitStatus: 94 CLOSED
CircuitStatus: 149 EXTENDED
CircuitStatus: 148 BUILT
CircuitStatus: 153 EXTENDED
.....
CircuitStatus: 153 BUILT
CircuitStatus: 134 CLOSED
...
...
Ending in many CLOSED statements
...
...
CircuitStatus: 134 CLOSED
</code></pre>
<p>the initial null wallet balance cannot be updated.</p>
<p>But you saw your balance change from a non-null value to null (then you saw <code>balance is not yet available</code>).    I suspect the balance is set to null while the tor circuit is broken, but I haven't reproduced that scenario yet.</p>
<p>When the circuit if finally reconstructed -- however long it takes -- the wallet balance is updated (confirmed by hitting my breakpoint @ <code>Balances#updateBalance</code>), and the cli can show the balance.  I think this is the problem you found.  If it is, you would have seen your balance after the tor circuit problems resolved themselves.   Eventually.</p>
<p>Right now, the :cli is telling the user that the "balance is not yet available", which is a correct statement, but not specific enough for a :cli user.  I am discussing with <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/freimair/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/freimair">@freimair</a> about how this problem is or might be categorized, and how this STATE could be communicated to the :cli user.</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/pull/4214#issuecomment-627416602">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNX2NXP55CVVJSMD67DRRFTHLANCNFSM4MUIOB4Q">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNSY4ZGU5QZ372H7LT3RRFTHLA5CNFSM4MUIOB42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEVSZ4GQ.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/pull/4214#issuecomment-627416602",
"url": "https://github.com/bisq-network/bisq/pull/4214#issuecomment-627416602",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>