Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fast exit fails after first signature #242

Open
johannbarbie opened this issue Aug 17, 2019 · 2 comments
Open

fast exit fails after first signature #242

johannbarbie opened this issue Aug 17, 2019 · 2 comments

Comments

@johannbarbie
Copy link
Member

observed behaviour:

metamask asks for 1 signature, then i see this in console:

index.09717d6ed8d875c1b82a.js:1 Uncaught (in promise) Error: Failed to subscribe to new newBlockHeaders to confirm the transaction receipts.
{}
    at Object._fireError (index.09717d6ed8d875c1b82a.js:1)
    at g (index.09717d6ed8d875c1b82a.js:1)
    at index.09717d6ed8d875c1b82a.js:1
    at Object.<anonymous> (index.09717d6ed8d875c1b82a.js:1)
    at index.09717d6ed8d875c1b82a.js:1
    at Array.forEach (<anonymous>)
    at WebSocket.connection.onmessage (index.09717d6ed8d875c1b82a.js:1)

receipt is never asked, also nothing in local storage:

Screen Shot 2019-08-17 at 4 28 05 PM

expected behaviour:

  • sig request for tx
  • sig request for sell receipt
  • period complete, exit tx by marketmaker
@troggy
Copy link
Member

troggy commented Nov 11, 2019

@johannbarbie which environment it is?

@troggy
Copy link
Member

troggy commented Nov 11, 2019

Failed to subscribe to new newBlockHeaders to confirm the transaction receipts.

related to poor websockets support. leapdao/leap-node#255
Using http should do the trick

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants