Open GoogleCodeExporter opened 8 years ago
Perhaps the DB input validation needs tightening. Or the plist generation logic
needs to more gracefully handle unexpected conditions (maybe just skip the
troublesome record).
In any case, there appears to be a too-long note in an entry.
Requests to the update url (<http://secrets.blacktree.com/plist>), receive:
<pre>
Traceback (most recent call last): File
"/base/python_runtime/python_lib/versions/1/google/appengine/ext/webapp/_webapp2
5.py", line 701, in __call__ handler.get(*groups) File
"/base/data/home/apps/blacktree-secrets/1.352126268324383173/secrets.py", line
185, in get some_secrets = secrets.fetch(200, 200*i) File
"/base/python_runtime/python_lib/versions/1/google/appengine/ext/db/__init__.py"
, line 2091, in fetch return list(self.run(limit=limit, offset=offset,
**kwargs)) File
"/base/python_runtime/python_lib/versions/1/google/appengine/ext/db/__init__.py"
, line 2263, in next return
self.__model_class.from_entity(self.__iterator.next()) File
"/base/python_runtime/python_lib/versions/1/google/appengine/ext/search/__init__
.py", line 463, in from_entity return super(SearchableModel,
cls).from_entity(entity) File
"/base/python_runtime/python_lib/versions/1/google/appengine/ext/db/__init__.py"
, line 1414, in from_entity return cls(None, _from_entity=entity,
**entity_values) File
"/base/python_runtime/python_lib/versions/1/google/appengine/ext/db/__init__.py"
, line 945, in __init__ prop.__set__(self, value) File
"/base/python_runtime/python_lib/versions/1/google/appengine/ext/db/__init__.py"
, line 599, in __set__ value = self.validate(value) File
"/base/python_runtime/python_lib/versions/1/google/appengine/ext/db/__init__.py"
, line 2744, in validate % (self.name, len(value), self.MAX_LENGTH))
BadValueError: Property notes is 528 characters long; it must be 500 or less.
</pre>
Original comment by garland....@gmail.com
on 3 Mar 2012 at 3:15
I am having this issue as well. It would seem this is something easy to fix:
there is a secret with notes longer than 500 characters somehow, and rectifying
this as well as other offending DB records will do the trick.
Original comment by fletc...@tomalty.com
on 12 Mar 2012 at 1:46
[deleted comment]
I did a fresh install of Mac OS X 10.7.3 and then reinstalled Secrets. Still
occurring. Stuck with default Secrets.
Original comment by m...@codycook.us
on 16 Mar 2012 at 11:55
Don't bother with trying to fix it on your system, people. This is a problem on
the server and is going to be the same for everybody on ALL systems until the
developer gets around to fixing it.
Original comment by fletc...@tomalty.com
on 17 Mar 2012 at 4:25
Original issue reported on code.google.com by
m...@codycook.us
on 28 Feb 2012 at 7:02Attachments: