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

An error occurred: Request not found #6669

Closed
stone212 opened this issue Oct 7, 2017 · 5 comments · Fixed by #6725
Closed

An error occurred: Request not found #6669

stone212 opened this issue Oct 7, 2017 · 5 comments · Fixed by #6725
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

Comments

@stone212
Copy link

stone212 commented Oct 7, 2017

I'm running:

  • Parity version: 1.7.2
  • Operating system: Debian 9
  • And installed: binaries

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.


@Vourhey
Copy link

Vourhey commented Oct 7, 2017

I'm having the same problem. Every transaction seems to be successful, but parity says "an error occurred: request not found"

Parity
version Parity/v1.7.2-beta-9f47909-20170918/x86_64-linux-gnu/rustc1.19.0

@5chdn 5chdn added F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M7-ui P2-asap 🌊 No need to stop dead in your tracks, however issue should be addressed as soon as possible. labels Oct 7, 2017
@5chdn 5chdn added this to the 1.8 milestone Oct 7, 2017
@5chdn 5chdn mentioned this issue Oct 10, 2017
67 tasks
@5chdn 5chdn modified the milestones: 1.8, 1.9, Patch Oct 12, 2017
@stone212
Copy link
Author

I am not having this problem after upgrading to 1.7.6.

@5chdn
Copy link
Contributor

5chdn commented Oct 18, 2017

yeah it's fixed in #6725

@davux
Copy link

davux commented Oct 30, 2017

@5chdn Can you confirm in which release this was fixed?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants