Skip to content
This repository was archived by the owner on Sep 18, 2020. It is now read-only.
This repository was archived by the owner on Sep 18, 2020. It is now read-only.

Blocknumber polling appears to be broken?  #213

Open
@jam10o-new

Description

@jam10o-new

Below is the relevant part of a bug report from a user on gitter

INFO 2019-02-27T15:54:26Z: parity_bridge_deploy: Deploying MainBridge contract
INFO 2019-02-27T15:54:26Z: bridge::deploy: sending MainBridge contract deployment transaction and waiting for 0 confirmations...
DeployMain: deployment transaction failed

Caused by:
SendTransactionWithReceipt: fetching last block number failed

Caused by:
Error(InvalidResponse("Error(\"expected value\", line: 1, column: 1)"), State { next_error: None, backtrace: InternalBacktrace { backtrace: None } })

Which seems to indicate that polling for blocknumber is failing - has there been any changes on the parity-ethereum side to explain this?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions