Vegacapsule block explorer: Number of issues blocking automation

[AndyWhiteVega]

Using block explorer within vegacapsule we keep running into issues when accessing the following pages in the UI:

[Blocks > Select Block with transactions] :
Bad Gateway 502: “Get \“http://localhost:26617///genesis\“: dial tcp 127.0.0.1:26617: connect: connection refused”.

[Transactions Page] :
Error on screen upon page load: Cannot fetch transaction: TypeError: Failed to construct ‘URL’: Invalid URL

[Oracles Page] :
Does not load anything - no network calls made

[Markets Page] :
Does not load anything - no network calls made

[Governance Proposals Page] :
Does not load anything - no network calls made

All of the above are working on testnet but not within vegacapsule.

All of the being undertaken in current sprint cannot be automated against until these issues are resolved.
The transactions stuff would be the most beneficial section to unblock first for QA

[AndyWhiteVega]

Currently preventing QA from automating against [Done] and [In Progress] items:
vegaprotocol/frontend-monorepo#397
vegaprotocol/frontend-monorepo#1627
vegaprotocol/frontend-monorepo#1682

[karlem]

hey @AndyWhiteVega, it is the frontend team who manages block explorer on Capsule. Can you please reports these issues to them? Thanks

[gordsport]

Closing this issue until:

• Add block explorer backend to vegacapsule #280

is implemented and tested.