question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How long we can install superset 0.16.0 using pip?

See original GitHub issue

How long we can install superset 0.16.0 using pip?

The network without VPN in China is so terrible, we cannot build supereset on local… image

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:8 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
xiaoideacommented, Feb 23, 2017

you can choose a pypi mirror in China, like Tsinghua, Douban, etc. Tsinghua: https://pypi.tuna.tsinghua.edu.cn/simple/

0reactions
tangshan-riskcommented, May 27, 2017

I have a similar trouble with Exit status 2: ERROR in ./~/_css-loader@0.28.3@css-loader!./~/_less-loader@4.0.3@less-loader/dist!./stylesheets/react-select/select.less Module build failed:

    &:hover {
            box-shadow: @select-input-hover-box-shadow;
        ^

Variable @select-input-hover-box-shadow is undefined in /Users/Alex/Desktop/superset/superset/assets/node_modules/_react-select@1.0.0-rc.5@react-select/less/control.less (line 64, column 14) @ ./stylesheets/react-select/select.less 4:14-162 @ ./javascripts/css-theme.js

npm ERR! Darwin 15.0.0 npm ERR! argv “/usr/local/bin/node” “/usr/local/bin/npm” “run” “build” npm ERR! node v6.10.3 npm ERR! npm v3.10.10 npm ERR! code ELIFECYCLE npm ERR! superset@0.17.6 build: NODE_ENV=production webpack --colors --progress npm ERR! Exit status 2 npm ERR! npm ERR! Failed at the superset@0.17.6 build script ‘NODE_ENV=production webpack --colors --progress’. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the superset package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! NODE_ENV=production webpack --colors --progress npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs superset npm ERR! Or if that isn’t available, you can get their info via: npm ERR! npm owner ls superset npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! /Users/Alex/Desktop/superset/superset/assets/npm-debug.log

Read more comments on GitHub >

github_iconTop Results From Across the Web

How long we can install superset 0.16.0 using pip? #2216
seems that the pypi doesn't contain version 0.16.0. I download the source code of 0.16.0 and setup it manually, but it's also a...
Read more >
Installing From Scratch - Apache Superset
Installing Superset with Helm in Kubernetes​​​ You can install Superset into Kubernetes with Helm. The chart is located in the helm/ directory.
Read more >
Installation & Configuration - apache-superset - Read the Docs
To enable support for long running queries that execute beyond the typical web request's timeout (30-60 seconds), it is necessary to configure an...
Read more >
Superset installation fails - python - Stack Overflow
According to pip install failing with: OSError: [Errno 13] Permission denied on directory, I tried this command line and it worked.
Read more >
Updating Superset
13980: Data health checks no longer use the metadata database as an interim cache. ... install Superset with the optional dependency prophet or...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found