-
Notifications
You must be signed in to change notification settings - Fork 32
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 in project setup #38
Comments
Quick debug question: what is the |
What is the output of:
Also - Does it work if you do:
|
npx: installed 342 in 15.354s
|
I'm able to reproduce this on a Macbook, but the error doesn't stop me from continuing. I'll keep looking into the exception, but you should be able to answer the next question, press "return", and continue on workflow. |
OK, that is at least one step forward. However, I can't get to the next question, when pressing enter. I have to Ctrl-C to get out |
Once the error message finishes printing, press the up arrow key and it should re-prompt you with the prod bucket question. Fill that out, then press Enter. I know it's a workaround, but at least you'll have a working template at the end of this. |
The up-arrow (or return key) works, but hitting then enter after the question is answered is not working here. Tried many keys to get going, all negative. |
Experiencing the exact same error/issues with the specs listed below OS: MacOS - Mojave 10.14.5 Reprompting the dev bucket input with ↑ and pressing Enter does nothing. |
Are you still getting it (as of basically now)? |
|
I have still the same issue. I even upgraded npm to the exact same specs as @albutko. I also created a new empty folder |
UPDATE: I jumped the gun on calling it resolved. I successfully ran the command for one visualization, but on further attempts this error persists. |
Nope, sorry, still getting the exact same error. Tried with different folders again It tells me -v |
What node/npm versions are y'all using? |
npm -version |
I am now actually getting a new error: |
I suspect that this: #72 is related, but will need further investigation to make sure. |
Can you try again? We made a ton of changes and I literally just redeployed. |
I also tried Anything else I should try? |
Does gsutil work for you outside of the tool?
…On Mon, Nov 25, 2019 at 4:42 PM Ralph Spandl ***@***.***> wrote:
MacBook-Pro-2:Data Studio Community Component ralph$ npx @google/dscc-gen viz
npx: installed 347 in 11.039s
? Project name DSCV
? What is your dev bucket? gs://
>> Error: Command failed with exit code 1 (EPERM): gsutil acl get gs://dscv
I also tried
npx --ignore-existing @google/dscc-gen viz
Anything else I should try?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#38?email_source=notifications&email_token=ACBYWS5VJWURVV3TXIFDJKTQVRWI5A5CNFSM4IFBHITKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFEJY3Y#issuecomment-558406767>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACBYWS2SQZ7SJSO7SXBI2YTQVRWI5ANCNFSM4IFBHITA>
.
|
I can do stuff like and do get a valid list back. Haven't tried anything else. |
And I managed to upload a file as well. |
I had the same issue. When you check how they validate permission in
gsutil acl get gs://<your bucket> which produces a 400 error if your bucket has a uniform bucket-level access. Try creating your bucket with gsutil mb -b off -l <your region> gs://<your bucket name> and it should work
|
This may be a trivial suggestion but have you tried running |
Confirmed, this worked for me |
Hi, in my case, my organization REQUIRES buckets to be created with uniform bucket-level access. So I cannot create one without, there is an org constraint on that. So basically I'm stuck even before starting. whoops. does anyone have another option please ? |
After having installed dscc-gen viz I am getting prompted with the project name.
However, when I insert the name of the dev bucket the setup returns an error.
I made however sure that
gs://dscc-test/testViz
is a valid address, I can download a file from this bucket (manifest.json)Error Message
The text was updated successfully, but these errors were encountered: