could not parse book from form: could not upload file: Post
https://www.googleapis.com/upload/storage/v1/b/statrecruit-application/o?alt=json=full=multipart:
oauth2: cannot fetch token: 401 Unauthorized
Response: {
"error" : "invalid_client",
"error_description" : "The OAuth client was not
Thanks George. Not quite the news I wanted, but better to know.
On 21 June 2017 at 01:13, 'George (Cloud Platform Support)' via Google App
Engine wrote:
> Hello Emlyn,
>
> The 15000 documents per minute quota is meant for the whole app. You can
> see in the
I'm currently using app engine images API and to serve images that I've
saved, I call
images.get_serving_url(blobkey
I want my users to be able to click on the download link I give them and
for the file to automatically download with the filename I've already
predefined but because of the
https://cloud.google.com/go/getting-started/tutorial-app
I am attempting to follow this tutorial and have been unable to get the
storage and OAuth2 portions working. I continually receive a 401
Unauthorized response when attempting to upload a file or login.
Then, I add my Client ID and Secret
I attempted to follow the bookshelf app tutorial and was able to get it
running and deployed. However, when attempting to upload images to the
storage and when activating the oauth2 portion I continually received error
Unauthorized responses (401).
This is the tutorial I followed. I also
Hi Adeel,
At point 2 of your reply above, the way you employ the "-dir=" parameter
does not correspond to any possible options, for cloud_sql_proxy. You can
compare and gather more relevant detail in the "Example proxy invocations
and mysql client connection strings" sub-chapter of the "About
Hello Emlyn,
The 15000 documents per minute quota is meant for the whole app. You can
see in the document you link to that the action is named "Adding documents
to Indexes", so generally, not one index or per index.
In the Java "Quotas" document
Hi Ignazio,
Glad to hear that the issue is now gone for good!
In case of similar issues in future, you can simply open another ticket in
the issue tracker.
On 19 June 2017 at 19:24, Ignazio Aleo wrote:
> Hi George,
>
> thanks for the reply (and sorry for my late one).
The project at the time was secure-gem .. I ported it to secure-gem2 but
secure-gem2 does not have the backing data..
On Monday, June 19, 2017 at 6:18:15 PM UTC-5, James Calfee wrote:
>
> Hi, sorry for the delay.
>
> The data-store upgrade was shortly after:
>
> 7/1/2015
>
> I have attached