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

Blocknumber polling appears to be broken? #213

Open
jam10o-new opened this issue Feb 28, 2019 · 1 comment
Open

Blocknumber polling appears to be broken? #213

jam10o-new opened this issue Feb 28, 2019 · 1 comment
Labels
F2-bug M4-core
Milestone
Arbitrary Message...

Comments

@jam10o-new
Copy link
Contributor

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?
@jam10o-new
Copy link
Contributor Author

bridge>src>send_tx_with_receipt.rs the poll function inside impl Future is not executing the loop in the right sequence.. it is executing AwaitBlockNumber before it is executing AwaitSendTransaction..

^ will investigate

@jam10o-new jam10o-new mentioned this issue Mar 5, 2019
Closed
4 tasks
@jam10o-new jam10o-new mentioned this issue May 29, 2019
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
F2-bug M4-core
Projects
None yet
Milestone
Arbitrary Message Passing MVP
Development

No branches or pull requests
1 participant
@jam10o-new