[google-appengine] Re: getting InvalidModuleError when trying to add job to taskqueue

2017-03-29 Thread Dewey Gaedcke 


OKI found the problem. The dev server was starting up without the 
taskqueue server running and so I guess the whole taskqueue package was not 
added to the google.api package

Seems like a better error would be useful in that case

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/6365d202-0969-402e-b654-f9331b0903cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: getting InvalidModuleError when trying to add job to taskqueue

2017-03-29 Thread 'Nick (Cloud Platform Support)' via Google App Engine 
Hey Dewey,

A thread like this, asking for technical support without determining 
whether it's the responsibility of your code or an issue with the platform 
/ SDK itself, should be made to Stack Overflow. An issue which you've 
determined to be in our code / within our responsibility to fix, should be 
posted to the Public Issue Tracker. This forum is not meant for technical 
support or issue reporting, but is meant for general and high level 
discussion of the platform and services, less specific and goal directed 
threads to which many users can contribute. 

I'd like to create a Feature Request in the Public Issue Tracker 
 from your post here to show an example of 
how to file a feature request for more clear errors once we've determined 
that an error needs a more clear message. The issue is, I'm not quite sure 
what was going wrong or what you did to fix it. Could you clarify what you 
saw, what you expected to see, what you saw instead, and what you did to 
change the issue?

Cheers,

Nick
Cloud Platform Community Support

On Wednesday, March 29, 2017 at 1:07:42 PM UTC-4, Dewey Gaedcke wrote:
>
> OKI found the problem. The dev server was starting up without the 
> taskqueue server running and so I guess the whole taskqueue package was not 
> added to the google.api package
>
> Seems like a better error would be useful in that case
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/7d636a50-557f-4485-a02c-41d505e3fb52%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: getting InvalidModuleError when trying to add job to taskqueue

2017-03-29 Thread Dewey Gaedcke 
Hi Nick...thanks for your reply.

I did also post this to SO but have received no responsesseems no one 
else has seen this
And since my code did not change, but I had recently upgraded the SDK, I 
was unclear what was causing the problem.  But here is the summary:

the backend for our mobile app (under app.yaml) calls these two lines:
from google.appengine.api import taskqueue
taskqueue.add(target='task', queue_name=GAEQ_FOR_PUSH_NOTIFY, url=url,params
=params )

That taskqueue.add() caused the error & resulting stack-trace shown above.

I had been starting my local dev-server via CLI like this:

dev_appserver.py --clear_datastore 0 app.yaml service_admin.yaml 
--logs_path=/tmp/gaelogs --log_level=debug


I didn't realize that I had grabbed an old example from our dev-onboarding 
document...and I should have been starting the local server like this:


dev_appserver.py --clear_datastore 0 app.yaml service_admin.yaml 
service_task.yaml --logs_path=/tmp/gaelogs --log_level=debug


once I also started the task microservice, the crash disappearedor at 
least I've not seen it again


service_task.yaml is the one that includes:

- url: /_ah/queue/deferred
  script: google.appengine.ext.deferred.handler
  login: admin

in the handlers section


all I can guess is that this caused the local environment to start up the 
task queuebut I really am only guessing...

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a5d6b3df-3ca1-4c18-9d06-ad4b6b8a021c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: getting InvalidModuleError when trying to add job to taskqueue

2017-03-30 Thread 'Nick (Cloud Platform Support)' via Google App Engine 
Hey Dewey,

That's an interesting pattern I can't say I've seen before. Now that you 
provide more details I see what you meant in your original post. I've 
attempted to reproduce this issue but haven't been able to observe it 
occurring. If you want to file a Feature Request for a better error message 
in the Public Issue Tracker , be sure to 
include a reproducing example app (you can produce this by stripping 
everything from your app that's proprietary / not necessary for reproducing 
the issue). We monitor the Public Issue Tracker regularly and would be 
happy to take your report.
 
Cheers,

Nick
Cloud Platform Community Support

On Thursday, March 30, 2017 at 12:29:13 AM UTC-4, Dewey Gaedcke wrote:
>
> Hi Nick...thanks for your reply.
>
> I did also post this to SO but have received no responsesseems no one 
> else has seen this
> And since my code did not change, but I had recently upgraded the SDK, I 
> was unclear what was causing the problem.  But here is the summary:
>
> the backend for our mobile app (under app.yaml) calls these two lines:
> from google.appengine.api import taskqueue
> taskqueue.add(target='task', queue_name=GAEQ_FOR_PUSH_NOTIFY, url=url,
> params=params )
>
> That taskqueue.add() caused the error & resulting stack-trace shown above.
>
> I had been starting my local dev-server via CLI like this:
>
> dev_appserver.py --clear_datastore 0 app.yaml service_admin.yaml 
> --logs_path=/tmp/gaelogs --log_level=debug
>
>
> I didn't realize that I had grabbed an old example from our dev-onboarding 
> document...and I should have been starting the local server like this:
>
>
> dev_appserver.py --clear_datastore 0 app.yaml service_admin.yaml 
> service_task.yaml --logs_path=/tmp/gaelogs --log_level=debug
>
>
> once I also started the task microservice, the crash disappearedor at 
> least I've not seen it again
>
>
> service_task.yaml is the one that includes:
>
> - url: /_ah/queue/deferred
>   script: google.appengine.ext.deferred.handler
>   login: admin
>
> in the handlers section
>
>
> all I can guess is that this caused the local environment to start up the 
> task queuebut I really am only guessing...
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ef68ecd0-88d9-488e-ad7f-11c36feed96b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.