This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
An error occurred: Request not found #6669
Labels
F3-annoyance 💩
The client behaves within expectations, however this “expected behaviour” itself is at issue.
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Milestone
I am deploying a test contract while running parity on --chain dev. I am using Truffle 3.4.11, migrating to the development network (localhost:8545) and this happens:
1 - Truffle command line migration seems successful and says "Saving successful migration to network" as expected.
2 - Parity, as expected, asks me to confirm each transaction with an empty password for the development account. I do this and each time (the contract actually is broken into many pieces) I see the Parity error saying:
"An error occurred: Request not found"
The error appears as the top, red bar in every box in the bottom right of the UI, where I just accepted each contract.
So my question is: what does this error usually mean and how can I debug it?
I have other evidence that the test migration was successful. The contract is behaving as expected locally via its own api. That is why I assume this is a Parity error and not truffle, or the contract.
The text was updated successfully, but these errors were encountered: