Cloud-Tasks | A very simple Palm webOS client for Remember The Milk | Frontend Framework library

Your task have two targets which is App Engine and HTTP. On HTTP, a URL is required as specified in creating HTTP target tasks.

The URL must start with 'http://' or 'https://'. To fix the problem, update your http_request:

In order to further contribute to the community I am posting the answer based on my comment above.

Firstly, you should try to upgrade the packages using the command:

pip install --upgrade pandas-gbq 'google-cloud-bigquery[bqstorage,pandas]'

Then, instead of using the to_dataframe() method you can use the read_gbq(), which loads data from BigQuery using the environment's default project, as follows:

When you refer to a Pub/Sub task, I understand you mean having an App Engine service subscribe to topic as a Push subscriber.

According to the Cloud Pub/Sub documentation, what you would consider a “queue” is basically Pub/Sub dynamically adjusting the rate of push requests based on the rate at which it receives success responses.

With push subscriptions, Pub/Sub considers a HTTP success response as an acknowledgement of the worker receiving the message. However, you have to keep in mind that the deadline to provide this response is initially determined by the ackDeadline of the subscription, which is 10 seconds by default, as mentioned in the Managing Subscriptions documentation.

According to the Receiving push messages documentation, if the App Engine subscriber does not reply with a success HTTP status code within the ackDeadline, Pub/Sub will retry delivery until the message expires after the subscription's message retention period.

Conveniently, you can set the ackDeadline for the push subscription to a maximum of 10 minutes, making it the same duration as the Python3 App Engine Standard with auto scaling deadline.

Regarding your question about the difference for the cron triggered requests, it is indeed how it is designed, but I would not be able to tell you why it is like that.

Also, for more information about the difference between Pub/Sub and Cloud Tasks you can refer to the official docs. Funnily enough, both Cloud Task and Pub/Sub docs contain a slightly different page talking about the different between the 2.

EDIT:

I decided to put the timeout deadline of Python2 apps to the test, and I confirmed that the limitation is indeed present even when receiving requests from a Pub/Sub push subscription.

I created 3 basic task handlers, that waited 80, 120, and 610 seconds to send a 200 http response respectively. When publishing to the topic, I noticed the following:

• As expected the service waiting for more than 10 minutes failed to acknowledge all the requests.
• The service waiting for 120s was successful in a few requests but failed in most of them.
• Strangely enough the service waiting for 80s successfully acknowledged all the requests.

This makes me believe the deadline for the Python2 is not such a hard limit as the documentation says. However, I still believe it is ideal to keep the documented deadline in mind when developing the apps, and be aware that, even for Pub/Sub tasks it will be somewhat applied.

As the runtime is most likely gonna be deprecated soon, I don’t think any changes in the documentation to specify the deadline for Pub/Sub tasks would be approved in time, as with Python3 there is no risk of App Engine terminating the request before the configured ackDeadline.

As per the Google docs, By default responseView is BASIC; not all information is retrieved by default because some data, such as payloads, might be desirable to return only when needed because of its large size or because of the sensitivity of data that it contains.

Thank You for this post, this is a bug in the existing Cloud Tasks UI and we are in the process of fixing this bug.

In the meantime the correct HTTP method of the task can be determined by running the following command:

gcloud beta tasks describe

https://cloud.google.com/sdk/gcloud/reference/beta/tasks/describe

The above command will show the correct HTTP method for the task.

Answer from: Google Cloud Tasks always set HttpMethod to GET when using HttpRequest as payload_type

You can also use the get task method to get more information.

For Cloud Datastore you can follow the instructions at https://cloud.google.com/datastore/docs/tools/datastore-emulator to use the local emulator instead of your production Datastore database.

As noted in https://cloud.google.com/tasks/docs/migrating, Cloud Tasks is not currently supported in an emulator.

As suggested in the Google Issue Tracker:

Hi, when you try to deploy, were you overwriting an existing version? If yes, could you please try to deploy a version with a new name instead of overwriting it? It seems the error you observed is a known issue so this will be a workaround for the moment as the App Engine engineering team works on this issue.

I tried deploying to a new version and it works, then I switch it back to overwriting the existing version and it works again. (*works for other applications as well.)

We are still not sure what is the cause of this sudden issue though.

P/S: I also added permission to my CI service in the bucket with "Storage Legacy Bucket Owner"