Quorum doesn't return a message error clearly specifying the cause of an error (from a user standpoint) when the transaction manager fails to Quorum (e.g: 400 bad request, ...).

System information

Release: 2.2.3

Expected behaviour

Helpful error message

Actual behaviour

invalid argument 0: json: cannot unmarshal non-string into Go value of type common.Hash

Balance sheet column headings should be the column's end date:

Balance Sheet 2020-07-03

                                      ||                                   2020-07-03
======================================++==============================================

But in the HTML output, it seems to be a date range instead:

Problem

After loading more account history, clicking the "refresh" button will reset the already loaded history

Steps to reproduce

1. Open https://explorer.solana.com/address/11111111111111111111111111111111?cluster=devnet
2. Click "Load more"
3. Click "Refresh"
4. Observe that the extended history is no longer visible

Proposed Solution

Refresh account history while retaining

this is the natural behavior of node-hid but we should backport this behavior to all other transports.

basically it's a failsafe for race conditions.

if you open() a transport, you are responsible to close() it in a finally, if an open() happens during that time it should throw if it concerns the same device (e.g. by path id / by uuid, ... depending on the transport)