dynamodb-janusgraph-storage-backend-*.zip file not found

[ramonPires]

I'm trying to run locally the getting started , https://github.com/awslabs/dynamodb-janusgraph-storage-backend#getting-started , but when I run this step, cp server/dynamodb-janusgraph-storage-backend-*.zip src/test/resources/dynamodb-janusgraph-docker , it says that the zip doesn't exists at server folder. The current version of docker in my machine is 17.06.0-ce-mac19 and my operating system is macOs Sierra.

[ramonPires]

When I run the command src/test/resources/install-gremlin-server.sh, I got the following output:

--2017-08-16 18:06:27--  https://github.com/JanusGraph/janusgraph/releases/download/v0.1.1/KEYS
Resolving github.com... 192.30.253.112, 192.30.253.113
Connecting to github.com|192.30.253.112|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/77385607/14114040-3636-11e7-9a95-91ca5bc24e3d?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20170816%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20170816T210546Z&X-Amz-Expires=300&X-Amz-Signature=f7e6d7a816a3366b25ca1213e03485e77bc955635ad84481e41fa762691ec1fd&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3DKEYS&response-content-type=application%2Foctet-stream [following]
--2017-08-16 18:06:27--  https://github-production-release-asset-2e65be.s3.amazonaws.com/77385607/14114040-3636-11e7-9a95-91ca5bc24e3d?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20170816%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20170816T210546Z&X-Amz-Expires=300&X-Amz-Signature=f7e6d7a816a3366b25ca1213e03485e77bc955635ad84481e41fa762691ec1fd&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3DKEYS&response-content-type=application%2Foctet-stream
Resolving github-production-release-asset-2e65be.s3.amazonaws.com... 54.231.120.43
Connecting to github-production-release-asset-2e65be.s3.amazonaws.com|54.231.120.43|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4440 (4.3K) [application/octet-stream]
Saving to: ‘KEYS.1’
KEYS.1                 100%[=========================>]   4.34K  --.-KB/s    in 0s
2017-08-16 18:06:28 (36.2 MB/s) - ‘KEYS.1’ saved [4440/4440]
gpg: key A39CC3ADAEAEF36E: "Theodore Ratte Wilmes (CODE SIGNING KEY) <twilmes@apache.org>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg: Signature made Thu May 11 11:19:58 2017 -03
gpg:                using RSA key A39CC3ADAEAEF36E
gpg: BAD signature from "Theodore Ratte Wilmes (CODE SIGNING KEY) <twilmes@apache.org>" 

[amcp]

I used the most recent versions of MacOS X and Docker on the HEAD commit of master branch and I was not able to reproduce this issue. Specifically, when running src/test/resources/install-gremlin-server.sh, I got the following output:

gpg: key A39CC3ADAEAEF36E: public key "Theodore Ratte Wilmes (CODE SIGNING KEY) <twilmes@apache.org>" imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: Signature made Thu May 11 23:19:58 2017 JST
gpg:                using RSA key A39CC3ADAEAEF36E
gpg: Good signature from "Theodore Ratte Wilmes (CODE SIGNING KEY) <twilmes@apache.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: D3C9 5553 EE39 B05E 350D  959C A39C C3AD AEAE F36E

The above suggests that the signature was OK.

[amcp]

Closing this issue as I was not able to reproduce. If you can give me the exact steps to reproduce, please add them to this issue and reopen the issue.