Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

Compile stuck at "compiling" #294

Open
jalme opened this issue Nov 8, 2019 · 3 comments
Open

Compile stuck at "compiling" #294

jalme opened this issue Nov 8, 2019 · 3 comments
Assignees
Labels
compilation bug solidity/vyper compilation issues

Comments

@jalme
Copy link

jalme commented Nov 8, 2019

Describe the bug
When compiling a contract it gets stuck at "compiling"

To Reproduce
Steps to reproduce the behavior:

  1. Open Atom
  2. Install etheratom package
  3. Install geth or Ganache
  4. Launch geth or ganache
  5. Configure etheratom to use geth or ganache
  6. Close and open Atom
  7. Compile

Expected behavior
Compilation ending successfully or with an error

Screenshots
Screenshot from 2019-11-07 11-43-34
Screenshot from 2019-11-07 11-45-16
Screenshot from 2019-11-07 15-25-29
Screenshot from 2019-11-07 19-14-36

Environment

  • Ubuntu 18.04.3 LTS
  • Atom 1.41.0
  • Etheratom version 4.5.3
  • apm 2.4.3
  • npm 6.2.0
  • node 10.2.1 x64
  • python 2.7.15+
  • git 2.17.1

Additional context
Uncaught (in promise) TypeError: Cannot read property 'content' of undefined at Web3Helpers.compileWeb3 (/home/jalme/.atom/packages/etheratom/build/main.js:989) at Web3Env.compile (/home/jalme/.atom/packages/etheratom/build/main.js:8060) at compileSubscriptions.add.atom.workspace.observeTextEditors.editor (/home/jalme/.atom/packages/etheratom/build/main.js:7995) at Workspace.observeTextEditors (/usr/share/atom/resources/app/static/<embedded>:11) at Web3Env.subscribeToCompileEvents (/home/jalme/.atom/packages/etheratom/build/main.js:7990) at HTMLElement.web3Subscriptions.add.atom.commands.add (/home/jalme/.atom/packages/etheratom/build/main.js:7915) at CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app/static/<embedded>:11) at CommandRegistry.dispatch (/usr/share/atom/resources/app/static/<embedded>:11) at CompileBtn._handleSubmit (/home/jalme/.atom/packages/etheratom/build/main.js:5024) at Object.ka (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:15) at qa (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:15) at ra (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:16) at wa (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:16) at Aa (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:17) at ya (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:17) at Ba (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:17) at Kd (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:81) at hb (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:283) at Qd (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:83) at Hc (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:84) at Pd (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:84) at exports.unstable_runWithPriority (/home/jalme/.atom/packages/linter-ui-default/node_modules/scheduler/cjs/scheduler.production.min.js:18) at fg (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:120) at fb (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:283) at Nd (/home/jalme/.atom/packages/linter-ui-default/node_modules/react-dom/cjs/react-dom.production.min.js:82)

@mikedeshazer
Copy link

Same

@zot
Copy link

zot commented Jan 1, 2020

I seem to have the same problem, here's my environment:

  • Etheratom 4.6.0
  • Atom 1.42.0
  • Ganache 2.1.2
  • Linux Pop!_OS 19.10

@sjana0 sjana0 closed this as completed Jan 2, 2020
@sjana0 sjana0 reopened this Jan 2, 2020
@0mkara 0mkara added the compilation bug solidity/vyper compilation issues label Apr 12, 2020
@sacredwx
Copy link

same

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
compilation bug solidity/vyper compilation issues
Projects
None yet
Development

No branches or pull requests

6 participants