Questions & Answers

Unable to build jupyterproxy in PNDA

0 votes
asked Jul 4 by arslan (200 points)
Hi all,

I am facing a issue while building PNDA 3.4 i am facing a below error when it try to build jupyterproxy.

`Error: invalid path 'jupyterproxy.release_version', missing key 'jupyterproxy' in struct.
--2017-07-04 11:06:35--  https://github.com/jupyterhub/configurable-http-proxy/archive/.tar.gz
Resolving github.com (github.com)... 192.30.255.113, 192.30.255.112
Connecting to github.com (github.com)|192.30.255.113|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-07-04 11:06:36 ERROR 404: Not Found.

tar (child): .tar.gz: Cannot open: No such file or directory`

Further i am unable to find the archive from the URL "https://github.com/jupyterhub/configurable-http-proxy/archive/"

Any solution for this problem?

1 Answer

+1 vote
answered Jul 4 by trsmith2 (3,160 points)
selected Jul 4 by arslan
 
Best answer
Are you certain you cloned all the repositories at release/3.4, including pnda.git?
commented Jul 4 by arslan (200 points)
I tried using build-jupyterproxy command manually, build file have URL request for jupyterproxy version using URL("https://raw.githubusercontent.com/pndaproject/platform-salt/release/3.4/pillar/services.sls") but it doesn't contain jupyterproxy.release_version.
commented Jul 4 by trsmith2 (3,160 points)
Unless you follow our advice and clone ALL the repositories at release/3.4 or switch to release/3.4 after cloning the build will not work.
commented Jul 4 by arslan (200 points)
I used the above command "git checkout tags/release/3.4" following is my new git log -1 output.

"commit e361ad729ad66b736849aa307599f85874fdbfd6 (HEAD, tag: release/3.4, tag: 0.1.1, origin/master, master)
Merge: e87d053 ea62156
Author: Julien Barbot <[email protected]>
Date:   Tue Jan 24 23:48:38 2017 +0100

    Merge pull request #15 from pndaproject/RELEASE-0.1.1
    
    Release 0.1.1
"
commented Jul 4 by trsmith2 (3,160 points)
Good, you'll now find that the jupyterproxy error doesn't occur because there's no reference to it in the release/3.4 code.
commented Jul 4 by arslan (200 points)
Thanks @trsmith2 and @James Clark it worked
...