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.

Sign up for GitHub

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

Jump to bottom

deploy to staging :) #423

Closed
A-Zak opened this issue Mar 13, 2019 · 3 comments
Closed

deploy to staging :) #423

A-Zak opened this issue Mar 13, 2019 · 3 comments
Labels
Estimate: Small
Milestone
v0 - demo on staging

Comments

@A-Zak
Copy link
Contributor

A-Zak commented Mar 13, 2019

No description provided.

@A-Zak A-Zak added this to the v0 - demo on staging milestone Mar 13, 2019
@jellegerbrandy jellegerbrandy mentioned this issue Mar 14, 2019
Closed
@tibetsprague
Copy link
Contributor

well this is an annoying bug, seems like an issue with an npm package, not sure why we are not seeing it locally though. or if we can fix. its in the websockets module depended on by web3-providers-ws

@tibetsprague
Copy link
Contributor

updating the version of web3 might fix it, but could also break other things

@jellegerbrandy
Copy link
Contributor

I've wanting to upgrade web3 for a while now but it has really nasty bugs in combinataion with the client: daostack/arc.js#124 for which I find no answers on google...

In any case, I resolved the deploy problem by disabling the cache according to these instructions: https://devcenter.heroku.com/articles/nodejs-support#cache-behavior

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Estimate: Small
Projects
None yet
Milestone
v0 - demo on staging
Development

No branches or pull requests
3 participants
@tibetsprague @A-Zak @jellegerbrandy