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

A JavaScript error occurred in the main process #150

Open
stone212 opened this issue Jun 29, 2018 · 6 comments
Open

A JavaScript error occurred in the main process #150

stone212 opened this issue Jun 29, 2018 · 6 comments
Labels
F3-annoyance The client behaves within expectations, however this “expected behaviour” itself is at issue. M0 - general Issue affecting Parity UI overall

Comments

@stone212
Copy link

Before filing a new issue, please provide the following information.

I'm running:

  • Parity client version: 0.2.7
  • Parity UI version: 1.10.x
  • Operating system: Linux
  • Installed via: deb
  • Fully synchronized: yes
  • Network: private
  • I tried to restart both Parity UI and Parity Ethereum client: yes

Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.

After creating an SSH tunnel to my server using these instructions (https://wiki.parity.io/Wallet-Remote-Access.html) the tunnel looks good. I get:

debug1: channel 4: free: direct-tcpip: listening port 8546 for 127.0.0.1 port 8546, connect from 127.0.0.1 port 57626 to 127.0.0.1 port 8546, nchannels 4

The Parity UI comes up but an error message requires me to click OK. Screenshot attached.

Please note that this error does not prevent me from using the Parity UI. I click "OK" and I am in the familiar UI and it seems to work normally.

@Tbaut Tbaut added F3-annoyance The client behaves within expectations, however this “expected behaviour” itself is at issue. M0 - general Issue affecting Parity UI overall labels Jun 30, 2018
@Tbaut
Copy link
Contributor

Tbaut commented Jun 30, 2018

Thanks for the report.

@amaury1093
Copy link
Contributor

Hey @stone212! Do you still have the screenshot by any chance?

@stone212
Copy link
Author

stone212 commented Jul 3, 2018

@amaurymartiny Here you are.

parityjserror

@axelchalon
Copy link
Contributor

should be fixed with a76cfef

@axelchalon
Copy link
Contributor

closing for now; should be fixed since Parity UI v0.3.0
let us know if you still have this error

@stone212
Copy link
Author

@axelchalon I still have this (well a very similar) error with Parity UI 0.34. Screenshot of current error attached.
34error

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. M0 - general Issue affecting Parity UI overall
Projects
None yet
Development

No branches or pull requests

4 participants