This error is not an issue with GCloud but is an error returned by your
operating system as it is not able to find the location of the 'gcloud.cmd'
file (e.g if using Windows).
You must add the directory path of the gcloud script (e.g C:\Program Files
(x86)\Google\Cloud SDK\google-cloud-sdk\bi
Yup. I'm having this issue too. Does anyone know of a way to fix it or a
good path to start down to solving this?
On Wednesday, April 10, 2013 8:37:16 AM UTC+1, Mahron wrote:
>
> Stops when threadsafe is set to "no". Must have something to do with
> threading I suppose.
>
>
>
> File "C:\Program
Actually it happens even if threadsafe : no. Just not as often.
--
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.co
Has anyone checked if 1.7.4 fixed this problem?
--
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/-/oEtxemVzCWMJ.
To post to this group, send email to
wtf. there's a tracker issue on this. what's the point in msg like
this one? please, stop.
On Sat, Dec 1, 2012 at 10:03 PM, GAEfan wrote:
> Very frustrating to have to restart the dev environment after changes!
> Wasting hours of developers' lives.
>
> Seems you're caching code. Impossible to tr
Very frustrating to have to restart the dev environment after changes!
Wasting hours of developers' lives.
Seems you're caching code. Impossible to troubleshoot in this environment.
Sometimes, the logging quits working, too.
+100
OSX 10.7.5, SDK 1.7.3
--
You received this message because
I am also seeing this issue on OSX
On Thursday, 29 November 2012 15:09:43 UTC+10, vivpuri wrote:
>
> Our team is also facing this issue. Mac OS 10.8.2 with SDK 1.7.3 and also
> on Windows 7.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group
Our team is also facing this issue. Mac OS 10.8.2 with SDK 1.7.3 and also
on Windows 7.
--
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/-/5Iy2yTuef
Same issue here on Windows 8
On Tuesday, November 13, 2012 9:20:57 PM UTC-8, Ajit wrote:
>
> For me too the same issue occurs. Need to restart the server in order to
> get the changes in the source.
>
> On Tuesday, November 6, 2012 9:25:41 AM UTC+5:30, GregF wrote:
>>
>> I just updated to SDK 1.7
For me too the same issue occurs. Need to restart the server in order to
get the changes in the source.
On Tuesday, November 6, 2012 9:25:41 AM UTC+5:30, GregF wrote:
>
> I just updated to SDK 1.7.3 running on Linux. At the same time I switched
> to the SQLite datastore stub, suggested by the de
Same issue here.
on MacOSX 10.8
--
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/-/0lfbY4PTjX4J.
To post to this group, send email to google-appengine
Issue #8383:
http://code.google.com/p/googleappengine/issues/detail?id=8383
Some suggestions of workarounds in there too. They didn't help me though.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
Has anyone created an issue on the tracker? I'd star it too. (Mac OS)
On Fri, Nov 9, 2012 at 2:11 PM, Nijin Narayanan wrote:
> +1 On windows 7. Same issue here. Because of this issue we have downgrade to
> 1.7.2. :(
>
> -Nijin Narayanan
> HP: +91 96 56 56 41 91
>
>
>
>
> On Fri, Nov 9, 2012 at 8
+1 On windows 7. Same issue here. Because of this issue we have downgrade
to 1.7.2. :(
-Nijin Narayanan
HP: +91 96 56 56 41 91
On Fri, Nov 9, 2012 at 8:38 AM, Kaan Soral wrote:
> +1 on Windows 7, on an old app, very annoying since it uses default
> datastore and a reset takes more than a mi
+1 on Windows 7, on an old app, very annoying since it uses default
datastore and a reset takes more than a minute
On Wednesday, November 7, 2012 10:02:28 PM UTC+2, Jason Collins wrote:
>
> I've been seeing this on Mac as well. Very misleading and annoying.
>
>
> On Tuesday, 6 November 2012 18:17
I've been seeing this on Mac as well. Very misleading and annoying.
On Tuesday, 6 November 2012 18:17:43 UTC-6, Jakob Holmelund wrote:
>
> We have the same issue. 4 guys running on ubuntu. This is really annoying..
>
> Den tirsdag den 6. november 2012 04.55.41 UTC+1 skrev GregF:
>>
>> I just upda
We have the same issue. 4 guys running on ubuntu. This is really annoying..
Den tirsdag den 6. november 2012 04.55.41 UTC+1 skrev GregF:
>
> I just updated to SDK 1.7.3 running on Linux. At the same time I switched
> to the SQLite datastore stub, suggested by the depreciation message.
>
> After t
Not sure if it is the same issue but my symptoms are similar. After
updating to SDK 1.7.3 on Windows 7 I have noticed that the compiled Python
files (.pyc files) are not always overwritten when I modify a source (.py)
file and it is executed. I never noticed this before SDK 1.7.3 and I have
not
I switched to sqlite3, here is the behavior:
Non administrator:
- Creates the rdbms file on custom location, populates the file
- Throws an "unable to read datastore file" exception
Administrator:
- Works perfectly
It wasn't working for non-sqlite3 even with the administrator privileges
and it
I'm on Windows, I've tried many things, It used to work flawless for years
I've tried changing the location of the datastore file, when the file
doesn't exist, it is not created, when I copy the existing datastore file,
it is read, but never modified, I don't think its a permission problem
sinc
Because they searched the groups and passed the default_partion argument to
the dev appserver.
On Sep 3, 2011 6:28 PM, "dop" wrote:
>
> I'm just amazed how little noise is there because of this issue. If I
> understand it correctly after upgrading to 1.5.2 evenybody's local
> datastore becomes e
I'm just amazed how little noise is there because of this issue. If I
understand it correctly after upgrading to 1.5.2 evenybody's local
datastore becomes empty. Yet very few seem to care. Weird...
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" g
Very nice move, Google team, very nice... Keeping developers busy with
really exciting stuff (unlike the actual developing), eh?
Joking aside, I was able to see the old data with the --default-
partition option, but because I run django-nonrel it's a bit tricky to
add this option support to every
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/-/_7jQ8A4UuWcJ.
To post to this group, send email to google-appengine@googlegroups.com.
To
Use this link instead:
http://code.google.com/p/googleappengine/downloads/detail?name=appengine-java-sdk-1.5.3.zip&can=2
It's the same file, but named to prevent confusion.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com | twitter.com/ikai
On Fri, Aug 19, 2011 at 1
We've pushed a new SDK here:
http://googleappengine.googlecode.com/files/appengine-java-sdk-1.5.3a.zip
I'm working on updating the docs, but this build should resolve the error.
When the docs are updated, I'll do a wider groups post.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
plu
wow cool fun stuff << http://j.gs/I9f >> i think you will like it
On Fri, Aug 19, 2011 at 10:16 AM, MindRaider wrote:
> Great! Thank you for logging the defect.
>
> -- martin
>
> On Aug 18, 9:59 pm, "Ikai Lan (Google)" wrote:
> > Yep, we're on it:
> >
> > http://code.google.com/p/googleappengi
Great! Thank you for logging the defect.
-- martin
On Aug 18, 9:59 pm, "Ikai Lan (Google)" wrote:
> Yep, we're on it:
>
> http://code.google.com/p/googleappengine/issues/detail?id=5612
>
> We might end up releasing a new SDK for this.
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App E
The file referred to in that log message is used for the experimental
SQL database support, not for the datastore stub.
Robert
On Sat, Jul 23, 2011 at 03:25, Cat wrote:
> One thing I know for sure now is that the following log message is
> bogus, it appears even if dev_appserver.py successfu
Many thanks Cat.
Just adding --default_partition= to the launch settings worked for me.
Using the Google App Engine Launcher;
Edit, Application settings.
In the box "Launch Settings" add --default_partition=
On Jul 23, 3:46 am, Cat wrote:
>
> SOLUTION
>
>
> 1.
That did the trick, Cat. Thanks!
On Jul 23, 2:46 am, Cat wrote:
>
> SOLUTION
>
>
> 1. USE --default_partition= BUT DO NOT INCLUDE THE QUOTES as mentioned
> in Matthew's post.
> 2. IGNORE THE INCORRECT LOG MESSAGE ... rdbms_sqlite.py:58] Connecting
> to SQLite da
SOLUTION
1. USE --default_partition= BUT DO NOT INCLUDE THE QUOTES as mentioned
in Matthew's post.
2. IGNORE THE INCORRECT LOG MESSAGE ... rdbms_sqlite.py:58] Connecting
to SQLite database ...
LauncherFlags:
--datastore_path=/Users/cat/repositories/appengine/my.d
One thing I know for sure now is that the following log message is
bogus, it appears even if dev_appserver.py successfully connects and
uses a store at a different location than the TMP directory.
INFO 2011-07-23 07:22:11,762 rdbms_sqlite.py:58] Connecting to
SQLite database '' with file '/var/
I tried the --default_partition="" flag but now validation.py is
throwing an exception:
Traceback (most recent call last):
File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/
GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/
google/appengine/tools/dev_appserver.
yup the sqlite updates don't quite seem to work.
i second that the release notes should be updated, the flag does seem to
work for me
cfh
--
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://g
Thanks, Matthew.
I was able to update to 1.5.2 and use my existing datastore by adding that
flag.
It would have been useful if the release notes had mentioned that this would
be necessary.
-Chrsi
On Fri, Jul 22, 2011 at 2:39 PM, Matthew Blain wrote:
> That's a clever way to update the appid. I
That's a clever way to update the appid. I do not know if it works for
all cases (e.g. it may not work for all reference properties (stored
keys)) but is a neat trick.
Another way to deal with it is to use the --default_partition="" flag
rather than using an older version of the sdk.
--Matthew
hi all,
i *think* that it is honoring your datastore location (though the log
message is incorrect), but the change to rename your application to
dev~ in development has just rendered all of our test data
useless.
after re-importing my test data it does look like it is stored where i ask
it t
I have tried to restore the datastore and the
GoogleAppEngineLauncher.app (with the SDK bundle inside) back to 1.5.0
but I cannot get it to run.
Its always the same error, as if the "downgrade" did not change the
python files.
Does anyone know how to get the SDK-version out of the running
appserver
+1 for me. I have tried deleting the application plist as detailed in
this issue
http://code.google.com/p/googleappengine/issues/detail?id=1187&q=datastore_path&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log
but no joy.
--
You received this message be
Cat, do you have backups of you datastore files from before you ran 1.5.2?
I was able to get running again by downgrading the SDK to 1.5.1 and
restoring my data files from a backup.
-Chris
On Fri, Jul 22, 2011 at 4:19 AM, Cat wrote:
> Update: (I'm going nuts)
> I downgraded to 1.5.1 (restored
I'm having a problem that may be related. I'm using django-nonrel which
sets the datastore path to .gaedata in the project directory.
When I start the server I get a log message that has the correct path:
INFO:root:Connecting to SQLite database '' with file
'/Users/me/workspace/myapp/.gaedata/rd
Update: (I'm going nuts)
I downgraded to 1.5.1 (restored GoogleAppEngineLauncher.app) and still
the same now ...
It seems that the upgrade to 1.5.2 did some permanent damage.
I am absolutely puzzled why --datastore_path= is ignored suddenly.
Here the full startup log:
cat$ /Applications/GoogleApp
Ok, finally I discovered what was happening... This is the code causing the
problem:
...
myobj.sendMessage(data);
alert('some 'message');
...
So the first sentence calls a method sending some objects (JSON formatted)
through a channel, and the second one shows an alert to trace my app.
Removin
I disabled threadsafe and AlwaysOn and it got worse. Many 500 errors on
instance startups, all with this message:
The process handling this request unexpectedly died. This is likely to
cause a new process to be used for the next request to your
application. (Error code 203)
When I re-enabled Al
Do these problems appear only with threadsafe on? Or do they only occur when
threadsafe is set to off?
Ikai Lan
Developer Programs Engineer, Google App Engine
Blog: http://googleappengine.blogspot.com
Twitter: http://twitter.com/app_engine
Reddit: http://www.reddit.com/r/appengine
On Thu, Apr 7
Master/Slave. But the exceptions don't seem to be related do datastore. Most
errors are with /_ah/warmup requests, and my startup process doesn't touch
the datastore.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group,
Are you using Master/Slave or HR?
2011/4/7 Sérgio Lopes :
> Hi Ikai!
> I didn't notice any performance issue here.
> However I'm experiencing a lot of errors lately during instance startup.
> I've AlwaysOn and the "Instances" panel clearly shows that 2 instances are
> always ok, with a large Age.
Hi Ikai!
I didn't notice any performance issue here.
However I'm experiencing a lot of errors lately during instance startup.
I've AlwaysOn and the "Instances" panel clearly shows that 2 instances are
always ok, with a large Age. But one of those instances is constantly being
shut down and res
Hey Ikai,
Thanks for the explanation about the pending queue, I think that may
be the most information I've ever seen about how that process works.
It would be great to have that information included somewhere in the
docs. At the minimum it can help understand certain behaviors we see
sometimes.
Hi,
It all appears very good so far from my experience - I haven't personally
noticed any drop-off in performance, only a massive decrease in the number
of instances spun-up and therefore a large drop-off of warm-up requests. A
big win!
Cheers,
Simon
--
You received this message because you
Wow, thanks for the feedback. Does anyone here have a negative experience
with thread-safe?
I'm asking because we had received some feedback that this resulted in
poorer performance. We don't believe this should be the case at all and want
to track down if and why this happens.
One huge benefit o
I've been using GAE 1.4.3 with on and AlwaysOn for a few days.
And my conclusion is that it almost solves all Cold Start problems we were
used to. Now I have fewer instances warmups and most of them are /_ah/warmup
request with no user suffering. In my tests, I had instances lasting more
than
Prospective search is not the same as full-text search.
You can read about it:
http://code.google.com/appengine/docs/python/prospectivesearch/
On Thu, Mar 31, 2011 at 13:31, tempy wrote:
> Hi,
> Just want to verify... the Prospective Search API is NOT the same
> thing as the "full text s
Is the JavaDoc for the Files API online somewhere? I noticed the Blobstore
Overview was updated to include some instructions (
http://code.google.com/appengine/docs/java/blobstore/overview.html#Writing_Files_to_the_Blobstore),
but I couldn't find the JavaDoc either in the SDK download or the on
What do Prospective and Retrospective searches refer to ?
On 31 March 2011 20:31, tempy wrote:
> Hi,
> Just want to verify... the Prospective Search API is NOT the same
> thing as the "full text search" API thats mentioned in the roadmap, is
> that right?
>
> I certainly hope so, as I very much n
Hi,
Just want to verify... the Prospective Search API is NOT the same
thing as the "full text search" API thats mentioned in the roadmap, is
that right?
I certainly hope so, as I very much need Retrospective and not
Prospective search.
--
You received this message because you are subscribed to t
Well, i my servlet methods (i use GWT RPC) do not use Thread specific
operations and they don't access any shared objects other than
Memcache objects, Session, or Datastore entities.
On 31 March 2011 18:20, Remigius wrote:
> Ice13ill,
>
> There's a short and a long long answer to your question.
>
Andrei, that's probably the right implementation, considering that an
application can run in multiple JVMs.
Where this sort of thing becomes very tricky is when people start using the
JVM's local memory as an even faster cache than Memcache and don't
synchronize access to data structures, which le
Ice13ill,
There's a short and a long long answer to your question.
The short one: If you don't already know what "proper thread
synchronization" is, leave the option switched off.
The long one: Switching it on allows multiple HTTP requests to be
handled concurrently by the same instance of your
http://code.google.com/appengine/docs/python/config/cron.html#Cron_and_App_Versions
On Thu, Mar 31, 2011 at 11:05, Sahid Orentino Ferdjaoui
wrote:
> Hello,
>
> - You can now configure the specific application version to which a task
> queue
> or cron job will send requests.
>
> How use t
Hello,
* - You can now configure the specific application version to which a task
queue*
* or cron job will send requests.*
How use this functionality?
Thank you
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, se
Yes, I did. about 10-25% of the time it would fail when using
blob_key to set a blobreference. I added a time.sleep(1) and problem
solved, so appears to be some type of consistency issue with the
blobinfo ??
On Mar 31, 6:58 am, Stephen wrote:
> On Thu, Mar 31, 2011 at 1:38 AM, JH wrote:
> > Be
On Thu, Mar 31, 2011 at 1:38 AM, JH wrote:
> Been looking forward to files api for a while!
>
> I have been playing with it and it seems there is an issue, I can't
> figure out if it's me or the files api...
>
> I kick off tasks which use the api to write about 300 files. It seems
> about 10% of
What dies thread safe really mean ? ("your application code needs to
use proper thread synchronization before you enable ").
Can someone give some hints?
On Mar 31, 10:53 am, Simon Knott wrote:
> Ah ignore my message, I've just tested it - in SDK 1.4.2 it throws an error
> and in SDK 1.4.3 it doe
Ah ignore my message, I've just tested it - in SDK 1.4.2 it throws an error
and in SDK 1.4.3 it doesn't. Cheers for the info, I should really have
guessed at that...
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group,
When you say it worked, how did you get confirmation? Is there a message,
or did it simply not throw an error?
--
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 unsu
I tried putting threadsafe: true in app.yaml and it worked. I put it as so:
application:
version: 1
runtime: java
threadsafe: true
--
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@goog
Is there anyway to set the *threadsafe* setting using the YAML configuration
for a Java app?
I could see that the appengine-web.xml docs had been updated, but can't see
a similar update to the YAML config page.
--
You received this message because you are subscribed to the Google Groups
"Go
FYI: To fix this I had to add a time.sleep(1) before setting my
blobreference property = to blob_key =
files.blobstore.get_blob_key(file_name) ...
maybe it takes a few hundred milliseconds for this to be available? or
some type of consistency issue when setting the reference property?
On Mar 30, 7
Been looking forward to files api for a while!
I have been playing with it and it seems there is an issue, I can't
figure out if it's me or the files api...
I kick off tasks which use the api to write about 300 files. It seems
about 10% of them fail, or when I run:
blob_key = files.blobstore.get
Incidentally, just experienced one of the sqlite related issues, and
added some comments
http://code.google.com/p/googleappengine/issues/detail?id=3124
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to g
Hi Robert
1-As I indicated, I do use appstats in local development (that´s where
I got the timing on the queries). The query rpc(keys_only) is very slow
(coudl take 3 seconds). db.get rpcs are very fast. Turning appstat
recording on or off makes no significant difference in the overall
performanc
Ubaldo,
1) use appstats, it may be slow because of (common) coding issues,
2) is your app making a call to get the map there? That could add a
bit of lag for sure.
Just some ideas.
Robert
On Sat, Dec 11, 2010 at 12:34, Ubaldo Huerta wrote:
> Hi Tim,
> Thanks for the thoughtful respon
Hi Tim,
Thanks for the thoughtful response. You're right that some of
this "bugs" refer just to sqlite related issues, and some indeed
highlight problems in the default file based datastore stub, not in
sqlite. The 2 most concerning seem to be the one about inequality
filters and the requiring in
I have found that the first query on my GAE/J development server
(which is a very simple one with one or zero "rows" of results) takes
approximately 5 seconds. After that, queries fly fast and well.
I guess that the first query involves some lazy initialisation.
Anyway, I have no complaints since
There are also a some pretty serious bugs in the default datastore
stub. My apps are fairly task-heavy; at this point I am no longer
able to the default stub -- I have to use sqlite. It works great, and
it is much faster.
Robert
On Fri, Dec 10, 2010 at 22:24, Tim Hoffman wrote:
> Hi
> I
Hi
I went through all of the raised issues in the tracker that you
referred to. (Some are actually not sdk sqlite issues).
One is raised by me (remote_api related so most people probably will
ever see it).
The other issues are corner cases, some people may experience them but
in all of my proje
Sqlite is allready a few years in python and used by countless people (busy)
sites etc., Gae is not inventing the wheel again (only some classes are
adapt to gae (new inherits)).
Parts of my development is an accounting package, never sees an unexpected
outcome in the figures (local and online, onl
Does that mean that you're not concerned about the maturity of the
sqlite implementation?
--
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-appeng...@googlegroups.com.
To unsubscribe from this group
Ubuntu, python2.6, sqlite on aged acer notebook works fast and well, 1700
product entities/images/stocks etc., lots of queries and updates for
test/development.
gr
wim
On Fri, Dec 10, 2010 at 3:30 PM, Ubaldo Huerta wrote:
> I've considered but if you look a the issue database, there are plenty o
I've considered but if you look a the issue database, there are plenty
of known bugs in the sqlite implementation. I'm afraid that the real
number is even higher. I hope someone at app engine team would soon
take the plunge to make sqlite the default database stub in the sdk.
That's the only way al
Are you using the sqlite backend ?
I am and have 100,000 entities in it and it is fine.
T
--
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-appeng...@googlegroups.com.
To unsubscribe from this gro
OT:
I actually really like this comment!
Coming from "Google" this makes it 2 times more awesome.
[Like!]
Maxim.
On Mon, Oct 18, 2010 at 10:25 PM, Ikai Lan (Google) <
ikai.l+gro...@google.com > wrote:
> No, I don't buy this argument. TortoiseSVN on Windows is about as easy as
> it gets. I hav
On Mon, Oct 18, 2010 at 6:25 PM, Ikai Lan (Google)
wrote:
> No, I don't buy this argument. TortoiseSVN on Windows is about as easy as it
> gets. I have never worked with a designer, web developer, product manager,
> salesperson, etc that could not learn the basics of how to use GUI source
> contro
Hi GAE developers,
as I've already said (without a reply) here:
http://googleappengine.blogspot.com/2010/10/new-app-engine-sdk-138-includes-new.html
the new Python documentation is buggy about the download_app last
minute drop out... pieces are still floating here: Python - Tools -
Uploading and
What about integrating the ability to deploy directly from version control,
and then gradually making that the recommended (and eventually, default)
path?
On Mon, Oct 18, 2010 at 4:25 PM, Ikai Lan (Google)
> wrote:
> No, I don't buy this argument. TortoiseSVN on Windows is about as easy as
> it
No, I don't buy this argument. TortoiseSVN on Windows is about as easy as it
gets. I have never worked with a designer, web developer, product manager,
salesperson, etc that could not learn the basics of how to use GUI source
control. And if that still doesn't work for you? Dropbox. Code download a
Look up the thread to read the numerous very valid concerns raised.
Jeff
On Mon, Oct 18, 2010 at 12:11 PM, Rafael Sierra wrote:
> On Mon, Oct 18, 2010 at 3:37 PM, Robert Kluin wrote:
>> Probably because about 50 people responded asking them to NOT include
>> that within a few hours.
>>
>> Most
It wasn't silently removed. Ikai stated they would re-evaluate the
idea based on feedback, and re-introduce it later.
--
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-appeng...@googlegroups.com.
Its not that hard. 5 minutes at max.
You can use hosted SVN service - http://unfuddle.com .
Desktop client:
Windows - http://tortoisesvn.net/downloads
Mac - SyncroSVN
On Oct 18, 3:11 pm, Rafael Sierra wrote:
> On Mon, Oct 18, 2010 at 3:37 PM, Robert Kluin wrote:
> > Probably because about 5
On Mon, Oct 18, 2010 at 3:37 PM, Robert Kluin wrote:
> Probably because about 50 people responded asking them to NOT include
> that within a few hours.
>
> Most likely, if you want that feature you need to go learn about
> version control.
> http://en.wikipedia.org/wiki/Revision_control
It's hard
Probably because about 50 people responded asking them to NOT include
that within a few hours.
Most likely, if you want that feature you need to go learn about
version control.
http://en.wikipedia.org/wiki/Revision_control
Robert
On Sun, Oct 17, 2010 at 00:09, mykhal wrote:
> hm, download_a
Can you explain in more detail what the "Average Latency" figure on
the admin console on the new Instances page means? It does not appear
to be documented anywhere.
I'm guessing it either means datastore latency (as latency is used
here
http://googleappengine.blogspot.com/2010/06/datastore-perf
hm, download_app functionality announced in prerelease seems to by
silently removed.. why?
On Oct 15, 5:44 am, Takashi Matsuo wrote:
> Hello App Engine Developers!
>
> We're very happy to announce that SDK1.3.8is released today. There
> are many new cool features, so please download the new SDK a
See
http://groups.google.com/group/google-appengine-java/browse_thread/thread/94d7e74a2e882b4b/65358a09ced5e1d2#
For GAE/Java there is another group:
http://groups.google.com/group/google-appengine-java
On Oct 16, 3:37 am, GoSharp Lite wrote:
> I am using Eclipse 3.5 to develop AppEngine and A
I am using Eclipse 3.5 to develop AppEngine and Android together,
since Android does not recommend using Eclipse 3.6.
Google Plugin for Eclipse 3.5 is still using SDK 1.3.7, can't update
new SDK 1.3.8.
Is there a way to manually install SDK 1.3.8 for Eclipse 3.5?
On Oct 15, 11:44 am, Takashi Matsu
Ignore the "AppStats" comment. I got it to work.
--
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-appeng...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubsc
"Support for login of multiple Google accounts within an app, and
longer login sessions."
For the above statement, in Admin Console > Application Settings >
Cookie Expiration, max time that you can choose is still 2 weeks. Was
that supposed to change too?
"Datastore Admin" - does not load for me
- Results of datastore count() queries and offsets for all datastore
queries are no longer capped at 1000.
I still get 1000 if I do:
count = Person.all().count()
Any help?
On Aug 18, 12:19 am, "Ikai L (Google)" wrote:
> Hey guys,
>
> This is just a heads up that App Engine SDK version 1.3.
1 - 100 of 182 matches
Mail list logo
