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
This build did not show a "condition" but the "status" did display. Unfortunately, some validators started appearing on the inactive table. To resolve this I delete all data from the database and resync'd. Everything appears fine except this problem.
I built bdjuno using the custom chain instructions. This worked without error and intially the status was "Status" was known but the "condition" was not. Nodes begain showing in the "inactive" tab on the validator page. If you click on any of the validators they will show as "active" with is correct.
I opened an Issue under BD2.0 (forbole/big-dipper-2.0-cosmos#607). We tested a query that shows the status is not being inserted in to the status table. See scrip in issue 607.
Expected behavior
Condition and status will be imported into the database and displyed properly in BD2.0 UI
The text was updated successfully, but these errors were encountered:
Bug description
This build did not show a "condition" but the "status" did display. Unfortunately, some validators started appearing on the inactive table. To resolve this I delete all data from the database and resync'd. Everything appears fine except this problem.
See: https://gravity-bridge.skynetexplorers.com/
Steps to reproduce
I built bdjuno using the custom chain instructions. This worked without error and intially the status was "Status" was known but the "condition" was not. Nodes begain showing in the "inactive" tab on the validator page. If you click on any of the validators they will show as "active" with is correct.
I opened an Issue under BD2.0 (forbole/big-dipper-2.0-cosmos#607). We tested a query that shows the status is not being inserted in to the status table. See scrip in issue 607.
Expected behavior
Condition and status will be imported into the database and displyed properly in BD2.0 UI
The text was updated successfully, but these errors were encountered: