-
Notifications
You must be signed in to change notification settings - Fork 249
utils.py python3 error with create: write() argument must be str, not bytes #2157
Comments
I also encounter this on Cloud Shell
|
I got the same error on Cloud Shell: datalab create mydatalabvm --zone us-east1-b Creating the network datalab-network |
I got the same error on Arch Linux ~
❯ datalab create writer
write() argument must be str, not bytes |
I got the same here on Cloud Shell: datalab create mydatalabvm --zone us-east1-b Creating the network datalab-network It worked before and suddenly it stopped working. |
I am encountering the same issue - command and stack trace below datalab --verbosity=debug --zone us-west2-b create new-instance
|
Root cause found - this is a GCP project I found my root cause - I had not enabled the google compute APIs on this project. You can confirm by doing the "datalab list" operaiton - this has the correct error handling and will give you a prompt to eanble the api. datalab list API [compute.googleapis.com] not enabled on project [############]. Enabling service [compute.googleapis.com] on project [############]... |
I have this same issue, but have Compute Engine API enabled. datalab list returns "Listed 0 items" Has anyone else seen this? |
I have the same exact issue on Cloud Console , I cant believe that GCP is unable to fix simple issues and dreams of competing with AWS and Azure , so much for nepotism in hiring in GCP , you can not get hired unless you are from a preferred country and from a specific majority religion from that country !!! |
I got same issue. It turn out the user I login doesn't have enough roles/permission to create instance. write() argument must be str, not bytes` |
I got the same error .. Here is a verbose message. Traceback (most recent call last): |
I tried to create a datalab instance from google cloud shell couple of months ago, it failed. Today, I tried it again. No surprise. It failed again. I am wasting my time. Below is the Tracebacks. Traceback (most recent call last): During handling of the above exception, another exception occurred: During handling of the above exception, another exception occurred: |
When I switched my instance name from test_instance to test-instance, the error stopped happening for me! So maybe Datalab doesn't like underscores. A new error cropped up, but I guess thats for a different issue... |
I had the same issue. In my case, it turned out that I was not logged in on gcloud inside my terminal, so even when I enabled all the APIs and checked whether the account is billing or not, datalab could not see it. Basically, |
I think the main issue here is that the error of child process cannot be correctly displayed. |
The same happened to me! Can't f* believe the underscore is a bug... |
It did not like the camel case name either for me.
|
We're having this issue as well, how is this not fixed after almost 2 years? |
Has anyone found a solution to this? After selecting region, I get Edit: I fixed this!!!! When I ran |
I think I was able to work .... by not including any capitals in the name of the file and changing the zone |
Running on OSX 10.13.6.
I have in my profile:
export CLOUDSDK_PYTHON=python3
when I run the command
datalab --verbosity=debug create new-instance
I get
The text was updated successfully, but these errors were encountered: