python
import Zope
app = Zope.app()
ob = app._p_jar['\000\000\000\000\000(\347\026']
print ob.id
print ob.__class__
... etc.
Chris Withers wrote:
Hi,
Another data point on these errors.
--
2001-05-18T11:01:44 ERROR(200) ZODB Couldn't load state for '\000\000\000\000\00
Chris McDonough wrote:
python
import Zope
app = Zope.app()
ob = app._p_jar['\000\000\000\000\000(\347\026']
print ob.id
print ob.__class__
Thanks, that worked, and sorry Chris, but I'm about to ruin your day :-S
app = Zope.app()
ob = app._p_jar['\000\000\000\000\000(\347\026']
print
I actually expected all along that it was mounted storage objects
causing the error (this happens with any mounted storage, not just the
one defined in CST).At least now we know it's the case. I'm
surprised no one thought of doing this earlier. ;-)
I suspect this has something to do with
Chris McDonough wrote:
I suspect this has something to do with the _p_jar attribute of the
mounted storage object becoming None at some point after a commit. That
said, I'm in over my head, and I'm going to need some help from others
at DC. Since this error rarely gets raised at the user
Chris McDonough wrote:
It is unfortunately one of the things lowering certain parts of NIP's
opinions
of Zope :-S
Ah I love FUD. Well, opine away. It has no actual effect on the system
that I can detect. Deinstalling CST will make it go away as well.
But, I think I now have confidence to
Chris McDonough wrote:
Chris McDonough wrote:
It is unfortunately one of the things lowering certain parts of NIP's
opinions
of Zope :-S
Ah I love FUD. Well, opine away. It has no actual effect on the system
that I can detect. Deinstalling CST will make it go away as well.
Easier
