embark

embark copied to clipboard

Bug Report

Summary

Following the quickstart tutorial https://embark.status.im/docs/quick_start.html

and embark run starts running and opens up the CLI Dashboard, but then returns an error saying Proxy: Error parsing string as JSON followed by a bunch of jsonrpc related junk.

IPFS, GETH, NVM, and everything else are installed and working, but embark is not.

Current behavior

the quickstart does not start, localhost:8000 is constantly in the "building" page but does not build

How to reproduce

Ubuntu 19.04

Install everything here, but skip the Rust, Python, and ML/DL sections and just sudo apt install python

• **https://github.com/burrrata/ubuntu-dev-env

Then try to follow the embark quickstart guide

Expected behavior

Wanted to quickstart

If you encounter an error, please create a logfile using the following command and post the output here

$ embark run --nodashboard --logfile log.txt --loglevel trace

Works up until this point:

Blockchain node is ready
geth: INFO [09-07|22:22:54.095] WebSocket endpoint opened                url=ws://127.0.0.1:8556

Proxy: Error parsing string as JSON '{"jsonrpc":"2.0","id":3,"result":{"difficulty":"0x1","extraData":"0x000000000000000000000000000000000000000000000000000000000000000093a317166d96b738bf2f4a88feca59d10e5ac5230000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000","gasLimit":"0x5fdfb1","gasUsed":"0x0","hash":"0xf9cc795843c5541e3c0f7d835086fcfcd040ea0ed82f831783e744002db21efe","logsBloom":"0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000","miner":"0x0000000000000000000000000000000000000000","mixHash":"0x00000000000'
Proxy: Error parsing string as JSON '00000000000000000000000000000000000000000000000000000","nonce":"0x0000000000000000","number":"0x0","parentHash":"0x0000000000000000000000000000000000000000000000000000000000000000","receiptsRoot":"0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421","sha3Uncles":"0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347","size":"0x26e","stateRoot":"0x2a3831c89b222da34e6573ad0a99f339c7dde1acbd5640f3ed342556ec01d787","timestamp":"0x0","totalDifficulty":"0x1","transactions":[],"transactionsRoot":"0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421","uncles":[]}}
'

Then continues on with Whisper, IPFS, etc...

Then more errors:

deploying contracts
Executing pre-deploy actions...
Proxy: Error parsing string as JSON '{"jsonrpc":"2.0","id":17,"result":{"difficulty":"0x1","extraData":"0x000000000000000000000000000000000000000000000000000000000000000093a317166d96b738bf2f4a88feca59d10e5ac5230000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000","gasLimit":"0x5fdfb1","gasUsed":"0x0","hash":"0xf9cc795843c5541e3c0f7d835086fcfcd040ea0ed82f831783e744002db21efe","logsBloom":"0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000","miner":"0x0000000000000000000000000000000000000000","mixHash":"0x0000000000'
Proxy: Error parsing string as JSON '000000000000000000000000000000000000000000000000000000","nonce":"0x0000000000000000","number":"0x0","parentHash":"0x0000000000000000000000000000000000000000000000000000000000000000","receiptsRoot":"0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421","sha3Uncles":"0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347","size":"0x26e","stateRoot":"0x2a3831c89b222da34e6573ad0a99f339c7dde1acbd5640f3ed342556ec01d787","timestamp":"0x0","totalDifficulty":"0x1","transactions":[],"transactionsRoot":"0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421","uncles":[]}}
'
IPFS available
====================================================================
[WS Request ID 3]: Original tx still not sent, considering it abandoned.
====================================================================
===================================================================
[WS Request ID 17]: No response received after 5s. Sending another tx to "push" it through...
Request ID 17 details: {"jsonrpc":"2.0","id":17,"method":"eth_getBlockByNumber","params":["0x0",true]}
===================================================================
IPFS available
====================================================================
[WS Request ID 17]: Original tx still not sent, considering it abandoned.
====================================================================
IPFS available
IPFS available
IPFS available
IPFS available

Then just keeps telling me that IPFS is available... but nothing happens

Please provide additional information about your system

OS - Ubuntu19 Embark Version latest Node Version --lts NPM Version latest

Sometimes issues are related to Embark's installation. Can you provide information on how Embark was installed?

npm i -g embark

Hi @burrrata. I'm wondering if the error is coming only form the proxy or from something else that might be missing.

To test, could you go in the blockchain confgi (default file is config/blockchain.js) and set proxy to false in development.

Let me know if it manages to get further or not.

Hi @burrrata. I'm wondering if the error is coming only form the proxy or from something else that might be missing.

To test, could you go in the blockchain confgi (default file is config/blockchain.js) and set proxy to false in development.

Let me know if it manages to get further or not.

proxy to false work

Do you lose any important features disabling the proxy option? Is this a bug or a configuration issue?

Do you lose any important features disabling the proxy option? Is this a bug or a configuration issue?

In Embark 4.1 and lower, you don't lose many features. You lose the transaction logger (it logs transactions made in a human readable way) and you lose the account list in the Dapp, but it's usually not a big deal.

As for if it's a bug, I would guess that it is, but we changed and improved the proxy in Embark 5 so hopefully it is fixed there.

We are planning on releasing the first alpha of Embark 5 this week, so stay tuned.