[google-appengine] How to update eclipse plugin to google app engine 1.6.5 sdk?
Last week, I couldn't upload Google App Engine because of version. In eclipse plugin, there was no update at google app engine. I connected http://dl.google.com/eclipse/plugin/3.7. Let me know how to update eclipse plugin? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Ab4rlGrWOc0J. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] URGENT main url path: "/", not serving.. but getting 200 response
Another thought: Perhaps if you just redirect your DNS to a "Down for Maintenance" page (not served by google) for a while, the cached page will be evicted sooner because nobody is hitting it... On Apr 27, 2012, at 4:31 PM, Joshua Smith wrote: > Let's review: > > Google has cached a blank version of your / page. > > The blank page is only about 12 hours old. The max-age is set to 1 year. So > this problem will go away on its own in a year. > > It really sucks to be you right now. :( > > You should try really, really hard to figure out how this happened. I've > never heard of anything like this on these lists, so it's likely that it's a > bug in your code someplace that can yield blank page with a 1 year timeout. > > If you repeat that telnet session, you can probably figure out more exactly > when the page was cached, then you can look at your logs to figure out what > caused it. Maybe. > > Getting the problem cleared would require some manual intervention from > google. They'd have to manually invalidate that cache entry. I'd bet money > that the Google App Engine team has no ability whatever to cause that to > happen. Upgrade to a $500/month enterprise account perhaps? > > I've been trying to think of a way to fix this using DNS, but I'm coming up > empty, short of changing your domain name. > > -Joshua > > On Apr 27, 2012, at 3:53 PM, Gregory Nicholas wrote: > >> yep.. bingo.. what are my options from here? >> >> >> >> On Fri, Apr 27, 2012 at 12:29 PM, Joshua Smith >> wrote: >> You could test this theory by hitting /?foo >> >> On Apr 27, 2012, at 3:17 PM, Matthew Blain wrote: >> >> > Typically a 204 with nothing run is simply a signal that your content >> > has been cached elsewhere in Google's network. If you responded with >> > cache-control: public with a max-age of something, it may be cached >> > until that expires. >> > Without futher info (such as an appid or the domain), it's hard to >> > tell what's going on. >> > >> > On Apr 27, 11:34 am, Gregory Nicholas >> > wrote: >> >> really need help.. i'm at a place where i can't really fix this on my >> >> own.. >> >> it's 11:00am.. been trouble shooting this since 9pm last night (thank god >> >> for adderall) >> >> >> >> *Preface (kinda):* >> >> >> >>- we've been working with appengine for a couple years now (haven't >> >> seen >> >>everything, but been through a lot of troubleshooting) >> >>- python 2.7, webapp 2.3, django 1.2, HRD >> >>- absolutely NO issues with local dev environ, production issue only >> >> >> >> *Issue / Symptoms:* >> >> >> >>- only the main url path: "/" for my app domain is not serving the >> >>request to my app >> >>- essentially breaks down to only the home page not working on >> >>http://www..com >> >>- the main url path for the appspot >> >>domain: http://.appspot.com serves >> >> - request is routed properly from the app.yaml to my request handler >> >>- on http://.com, any request to a subpath STILL WORKS! >> >> - ex: http://< domainname >.com/user/login serves, works >> >>- the request IS hitting my application: >> >> - attached is a screen shot of my app logs, where the main path >> >> serves >> >> - not hitting my app.yaml file, and not routed to any request >> >> handlers >> >> - appears as though my code is never being executed for the >> >> request >> >> >> >> *What I've tried:* >> >> >> >>- i telnet'ed and tracerouted the domain name to rule out it being a >> >> DNS >> >>issue >> >> - see attached terminal screenshot >> >>- i've redeployed my app several times >> >>- i reverted the default version to a previous version >> >>- i've shutdown any instances several times >> >>- i switched from automatic instance allocation to manual, switching >> >>from F1 to F2 classes >> >> >> >> PLEASE HELP!!! >> >> >> >> Screen Shot 2012-04-27 at 11.14.15 AM.png >> >> 193KViewDownload >> >> >> >> Screen Shot 2012-04-27 at 11.31.23 AM.png >> >> 156KViewDownload >> > >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Google App Engine" group. >> > To post to this group, send email to google-appengine@googlegroups.com. >> > To unsubscribe from this group, send email to >> > google-appengine+unsubscr...@googlegroups.com. >> > For more options, visit this group at >> > http://groups.google.com/group/google-appengine?hl=en. >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To post to this group, send email to google-appengine@googlegroups.com. >> To unsubscribe from this group, send email to >> google-appengine+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/google-appengine?hl=en. >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine"
[google-appengine] Re: App Engine 1.6.5 Released
Sources on SVN have been updated too, thank you! http://code.google.com/p/googleappengine/source/browse/ Interesting features ahead: http://www.google.com/url?sa=D&q=http://code.google.com/p/googleappengine/source/browse/trunk/java/src/main/com/google/appengine/api/socket/&usg=AFQjCNES0GWahEiGl-QyGx2AMILX_n0dBA -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] URGENT main url path: "/", not serving.. but getting 200 response
*Richard Watson's *post was money.. ackkk.. someone unwittingly let the cache-control header slip into a base request handler.. thnx everyone.. On Sunday, April 29, 2012 12:53:15 AM UTC-7, Richard Watson wrote: > > What if Gregory put (e.g.) Cloudflare in front of the app and used it to > fetch "app" requests and serve them as "www" (I assume that's possible). > This way, people continue to see www and can add www links. Can try it as > a short-term solution while you tinker with the setup and/or wait for the > edge cache to sort itself out. > > It's quite possible that Google's edge cache caches for a maximum period > shorter than a year due to demand/bandwidth priorities, so maybe this'll be > solved in a week or month. > > On Saturday, April 28, 2012 10:13:26 AM UTC+2, alex wrote: >> >> I think you can actually do it without manual intervention from Google >> internally: >> >> Let's say your app (with cached blank page) is currently accessible as >> www.example.org >> >> 1. make sure you remove "cache-control: public ..." headers from the >> response >> 2. add a mapping that will make your app accessible as app.example.org >> 3. like Joshua suggested, change www CNAME into www A DNS record pointing >> somewhere else, where you do a simple (maybe even permanent) redirect to >> app.example.org >> >> Even though it seems like your blank page is cached for a long time now, >> www DNS record will expire sooner (normally 24 ours if you haven't changed >> TTL) >> >> Hope that helps. >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/llofFYky_t8J. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Testing blob migration
i've tried this again with 1 other app and 2 other destination apps. all are having the same result. no __BlobInfo__ or __BlobMigration__ tables in the datastore, nothing in the blob viewer. Are there settings that might have prevented the blob copy? thanks so much, christian On Friday, April 27, 2012 6:06:30 PM UTC-7, c h wrote: > > Hello, > > I'm trying to test migration from master/slave to HRD. I just ran the > migration and selected the option for migrating blobs. i got the > notification that the migration is complete, but i don't see any blobs in > the blob viewer of my destination app. has anyone else had this > experience? what can i do to get my blobs to show up in my copied app? > > thanks, > > christian > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/9pfhXiJqKx0J. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] backend running really slow - taskqueue.add() takes much longer on the backend than on front-end
My backed is triggered every 90 minutes from a cron job, and usually takes between 10 and 20 minutes to do its work. Since April 26th, it seems to be taking 30 minutes at best, and ~100 minutes at the worst case. On average, its about a 5x increase in run-time. So, I investigated to try to find out which API calls are contributing the most to this increase. It seems that its a call to taskqueue.add() that's gotten really slow. So, I ran a smaller version of my backend task on a front-end instance first, and then again on the backend instance to try to compare run-times. And yes - the exact same HTTP request took 406 seconds on the backend, and only 7.5 seconds on the front-end instance. This particular HTTP request leases a bunch of tasks from a pull queue, and then processes them and re-inserts them back into the same pul queue. I put logging.debug() calls before and after taskqueue.add(), and noticed that on the front-end that API call takes on average 8ms, while on the backend it takes on average 600ms (around 2 seconds, worst-case). This behavior has been happening since April 26th. Anyone else seen this? Regards - Rishi -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] make backup/restore a first-class citizen (please star me)
Please consider starring this feature request: http://code.google.com/p/googleappengine/issues/detail?id=7428 Remember when you first used Time Machine in Mac OSX and were blown away by how simple it was to use and the confidence you were left with in its ability to get the job done? Have you ever once questioned its ability to protect your data? Have you scoffed at the fact that Windows did not have an integrated backup/restore system for all those years and marvelled at how they could have overlooked something so important? I'm really happy that Google has started paying some serious attention to this part of their system, but I'd like to see a much more integrated solution. It would really help me make a case for App Engine when dealing with enterprise clients, as well as raise my own confidence level. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] backend termination question
Does anyone know what this means: "*Process terminated because the backend took too long to shutdown*" My backend is woken up every 90 minutes by a cron job and typically takes 30 minutes to complete. Although sometimes this time can go up to 60 minutes. The error above has occurred multiple times - sometimes 10-15 minutes into the processing. Any ideas? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] SMALLEST and FASTEST Template Engine on Python
Also, jinja2 has C-accelerated escaping (via markupsafe) in python27, which should add to the speed. On Wednesday, 25 April 2012 20:09:07 UTC+10, Takashi Matsuo (Google) wrote: > > Hi Ayan, > > I have not tried it myself yet, but how about tenjin? > http://www.kuwata-lab.com/tenjin/ > > Besides that, if you can use python2.7 runtime, jinja2 is now bundled > in the SDK, and should be fast thanks to its bytecode cache, which is > only available with python2.7 runtime. > > However, in most cases, the difference here might be negligible > compared to the cost of various RPCs. > > -- Takashi > > On Wed, Apr 25, 2012 at 6:36 PM, Ayan Debnath wrote: > > Dear Friends, > > > > > > Can you please suggest me which one is the SMALLEST and FASTEST template > > engine for Google App Engine on Python2.5 and Python2.6 ? > > > > I am looking for the SMALLEST and FASTEST. > > > > Thank you > > Ayan Debnath > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to google-appengine@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine+unsubscr...@googlegroups.com. > > For more options, visit this group at > > http://groups.google.com/group/google-appengine?hl=en. > > -- > Takashi Matsuo | Developer Advocate | tmat...@google.com | 03-6384-9224 > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/TyRsx4_k01QJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Re: Does the Log Viewer actually work for anyone?
The symptom that really annoys me is when you have an error on your dashboard, click on it and there's nothing in the logs. Poof! It never happened! Even fixing that use case would be great, something is putting it on the dashboard, maybe include the time of one of the errors on the dashboard so we can drill down that way? Time queries work well. On Tuesday, April 17, 2012 11:33:24 PM UTC+1, Jason Collins wrote: > > Is it just me, or does the Log Viewer searching basically not work? > > I have my log storage configured to give me about 11 days of logs, but > I can rarely actually find stuff (that I _know_ occurred within my > window) by searching - both regex- and label-based searching. We run > at about 100+QPS, so trying to catch something in action is basically > impossible. > > I'm guessing the log indexing runs async to the log entries > themselves, and it's just not able to keep pace, or the indexing jobs > themselves are just failing. > > Does anyone actually have any luck searching the logs in the Log > Viewer on a reasonably high rate application? > > j -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/xL5vZb-FRG4J. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
[google-appengine] Is HSTS disabled for a reason? Can't set the Strict-Transport-Security header
I was playing around with this site: https://www.trustworthyinternet.org/ssl-pulse/ and noticed that my app engine site, (which gets an A, well done Google but I expect nothing less :-) wasn't listed as supporting HSTS when I thought it did. So I investigated and found that my HSTS header which used to work doesn't work any more. I have no idea when it stopped working, need to add it my test suite. Is there a reason for this? It isn't in the blacklist here: https://developers.google.com/appengine/docs/python/tools/webapp/responseclass#Disallowed_HTTP_Response_Headers Issue entered: http://code.google.com/p/googleappengine/issues/detail?id=7427 thanks. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/O8lrcPJDRXMJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Re: [google-appengine] URGENT main url path: "/", not serving.. but getting 200 response
What if Gregory put (e.g.) Cloudflare in front of the app and used it to fetch "app" requests and serve them as "www" (I assume that's possible). This way, people continue to see www and can add www links. Can try it as a short-term solution while you tinker with the setup and/or wait for the edge cache to sort itself out. It's quite possible that Google's edge cache caches for a maximum period shorter than a year due to demand/bandwidth priorities, so maybe this'll be solved in a week or month. On Saturday, April 28, 2012 10:13:26 AM UTC+2, alex wrote: > > I think you can actually do it without manual intervention from Google > internally: > > Let's say your app (with cached blank page) is currently accessible as > www.example.org > > 1. make sure you remove "cache-control: public ..." headers from the > response > 2. add a mapping that will make your app accessible as app.example.org > 3. like Joshua suggested, change www CNAME into www A DNS record pointing > somewhere else, where you do a simple (maybe even permanent) redirect to > app.example.org > > Even though it seems like your blank page is cached for a long time now, > www DNS record will expire sooner (normally 24 ours if you haven't changed > TTL) > > Hope that helps. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/MZSkx7g6mYYJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
