Matt Solomon
@msolomon44_twitter
Good call on testing that
Jonathan Rainville
@jrainville
If you want, you can link me a repo where I can test running it and the commands you used and I'll try to debug on Embark's side
Matt Solomon
@msolomon44_twitter
I wonder what changes about ganache when using that fork that causes it to not work
Yea give me a minute to set it up
Jonathan Rainville
@jrainville
I'm not sure, last time it was Embark that failed because somehow, using fork, the block 0 didn't exist
Matt Solomon
@msolomon44_twitter
Just started it today so only have a local git repo at the moment
Matt Solomon
@msolomon44_twitter
Sorry for the delay, somehow my GitHub SSH keys were no longer configured so had to fix that
I'll add a README adding the commands that work/don't work
Jonathan Rainville
@jrainville
Ok thanks. I'll test in about 20 minutes
Matt Solomon
@msolomon44_twitter
Awesome, thanks a lot for the help
Matt Solomon
@msolomon44_twitter
Just added a simple README, pretty much just sums up what we discussed here, and says which pair of commands works and which doesn't
Jonathan Rainville
@jrainville
Cool perfect
Jonathan Rainville
@jrainville
@msolomon44_twitter Just letting you know that I found the problem. It lies in Embark, it's the same as I had before, but my fix ended up not being good enough. I'm working on a new fix and with luck, we can release a patch tomorrow ;)
Jonathan Rainville
@jrainville
@msolomon44_twitter Just pushed a PR that fixes the issue. I'll let you know once it's merged and released.
You will see, once you have the fix, you will still get an error telling you something hapenned, but it only affects the deploy-tracker and all your tests will still pass.
Basically, somehow, with --fork and mainnet, all the getBlock web3 functions return that error, so I'm guessing something is bugged on Ganache's side
Matt Solomon
@msolomon44_twitter
Oh awesome that a quick fix, thanks so much! Looking forward to testing it out
Out of curiosity, if the underlying cause is an issue with Ganache how are you working around it?
Jonathan Rainville
@jrainville
The error is hapenning in the deploy-tracker, which is useless for tests, so I just print an error explaining what is hapenning, but I keep going ignoring the error. That way, everything keeps working expect the deploy-tracker
Matt Solomon
@msolomon44_twitter
Ah yep, I see it in the pull request, seems straightforward enough. Might be good to open an issue on the ganache-cli repo too.
Looks like it was merged already too, any idea when the release should be out?
Jonathan Rainville
@jrainville

any idea when the release should be out?

Hopefully today. We have a couple of dependency PRs waiting to be merged that'll likely ship with it too

Matt Solomon
@msolomon44_twitter
Sweet, really appreciate the quick turnaround!
Jonathan Rainville
@jrainville

Might be good to open an issue on the ganache-cli repo too

Yeah, it's a good idea. I'll do it later

No problem, it's a pleasure
RJ Ewing
@ewingrj
I'm running into issues w/ embarkjs connecting via wss in my app. I can connect via web3 directly just fine.
Error while loading the app: Could not establish a connection to a node.
is there any known issues connecting via wss?
Jonathan Rainville
@jrainville
No known issues, but we also didn't test much if at all with wss
Embark Bot
@embarkbot_gitlab
iurimatias@discord how are you connecting to it?
iurimatias@discord is this embarkjs being used directly as a lib, or as part of embark?
RJ Ewing
@ewingrj
I'm using create-react-app w/ embarkArtifacts in the react src dir. In my app I load EmbarkJS from embarkArtifacts/embarkjs
Jonathan Rainville
@jrainville
Does it work with just ws? Just to try to pinpoint the problem
Ah, nvm, I'm pretty sure we have a bug with wss
Embark Bot
@embarkbot_gitlab
iurimatias@discord this rings a bell
iurimatias@discord I think we fixed it recently but it might be in v5
Jonathan Rainville
@jrainville
Yeah, you just worked on dappConnection, so it must be fixed in v5, but we should patch it in 4.1
Jonathan Rainville
@jrainville
FYI @ewingrj I'm going to fix it right away and it can go in the patch we plan on releasing soon :tm:
Embark Bot
@embarkbot_gitlab

3esmit@discord i keep getting this error:

not sure what happened, I just trying to update my project to latest embark

3esmit@discord topic-democracy$ npx embark build development Building using the development environment. Did you forget to add an environment? eg: `embark build testnet` loading solc compiler... IPFS node not found, attempting to start own node Starting ipfs process Starting Blockchain node in another process compiling solidity contracts... (node:30589) UnhandledPromiseRejectionWarning: TypeError: _web.default.providers.WebsocketProvider is not a constructor at Proxy.serve (/home/ricardo/Documents/GitHub/topic-democracy/node_modules/embark-blockchain-process/dist/proxy.js:276:24) (node:30589) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:30589) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
3esmit@discord TypeError: callback is not a function at /home/ricardo/Documents/GitHub/topic-democracy/node_modules/web3/lib/web3/property.js:119:13 at /home/ricardo/Documents/GitHub/topic-democracy/node_modules/web3/lib/web3/requestmanager.js:89:9 at XMLHttpRequest.request.onreadystatechange (/home/ricardo/Documents/GitHub/topic-democracy/node_modules/web3/lib/web3/httpprovider.js:118:13) at XMLHttpRequest.dispatchEvent (/home/ricardo/Documents/GitHub/topic-democracy/node_modules/xhr2/lib/xhr2.js:76:20) at XMLHttpRequest._setReadyState (/home/ricardo/Documents/GitHub/topic-democracy/node_modules/xhr2/lib/xhr2.js:422:14) at XMLHttpRequest._onHttpResponseEnd (/home/ricardo/Documents/GitHub/topic-democracy/node_modules/xhr2/lib/xhr2.js:615:14) at IncomingMessage._response.on (/home/ricardo/Documents/GitHub/topic-democracy/node_modules/xhr2/lib/xhr2.js:567:23) at IncomingMessage.emit (events.js:203:15) at endReadableNT (_stream_readable.js:1129:12) at process._tickCallback (internal/process/next_tick.js:63:19)
Embark Bot
@embarkbot_gitlab
michaelsbradleyjr@discord which version of embark?
Embark Bot
@embarkbot_gitlab
Embark Bot
@embarkbot_gitlab
3esmit@discord btw, my older version of the project broke aswell, so I cannot work with past version of embark, I get this error:
topic-democracy$ npx embark run
Cannot find module 'web3'
Embark Bot
@embarkbot_gitlab
3esmit@discord Not sure exactly what I did but I managed to fix the error with the above version, I did a clean up in all dependencies in packages.json and reset the node_modules
Matt Solomon
@msolomon44_twitter
@jrainville Just wanted to let you know I built embark from the latest master and can confirm it's working as expected -- throws the error message, but the tests still work :thumbsup:
Thanks again!
Jonathan Rainville
@jrainville
@msolomon44_twitter Great. Sorry the release is not out yet, we found some other issues we want to fix with the same release
Matt Solomon
@msolomon44_twitter
No worries at all