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.

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

error installing msa #2

Open
gdroc opened this issue Nov 29, 2016 · 2 comments
Open

error installing msa #2

gdroc opened this issue Nov 29, 2016 · 2 comments

Comments

@gdroc
Copy link

gdroc commented Nov 29, 2016

npm 4.0.2
biojs2galaxy 0.0.7

I've installed biojs2galaxy globally, and am now trying to install the MSA module, but getting the following errors:
$ biojs2galaxy msa -o config/plugins/visualizations/
#tmpdir: /tmp/tmp-441816p784gw
[ 'galaxy-biojs', 'galaxy-vis' ]
err { [Error: ESOCKETTIMEDOUT]
code: 'ESOCKETTIMEDOUT',
connect: false,
url: 'http://registry.nodejitsu.com/-/_view/byKeyword?startkey=%5B%22galaxy-biojs%22%5D&endkey=%5B%22galaxy-biojs%22%2C%7B%7D%5D&group_level=3&descending=false&stale=update_after',
statusCode: 500,
errors: [],
body: undefined,
data: {},
remaining: 0,
ratereset: 0,
ratelimit: 0 }
err { [Error: ESOCKETTIMEDOUT]
code: 'ESOCKETTIMEDOUT',
connect: false,
url: 'http://registry.nodejitsu.com/-/_view/byKeyword?startkey=%5B%22galaxy-vis%22%5D&endkey=%5B%22galaxy-vis%22%2C%7B%7D%5D&group_level=3&descending=false&stale=update_after',
statusCode: 500,
errors: [],
body: undefined,
data: {},
remaining: 0,
ratereset: 0,
ratelimit: 0 }
workmen info # pkgs 0

Any insight on how to solve the problem?

Thanks!

@wilzbach
Copy link
Member

Hmm I think since the MSA component no longer uses browserify the automatic bridge can't work. Though your problem seems to be more a network issue.

In any case, you might want to see my comment at a previous issue with a static zip archive of the MSAViewer galaxy plugin.

@MatthewRalston
Copy link

Bump. Still not working. a simple GET on the uri above also sputters to oblivion. It's probably not your code and actually the msa package. My guess is that something is internally wrong with the 'nodejitsu' domain servers. This may render this entire application un-usable.

FWIW, I am working from behind a proxy. But I can't find anywhere in your code where you're using non-standard node components that don't recognize the environmental variables HTTP_PROXY etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants