On Feb 24, 2007, at 5:20 AM, Wolfram Stebel wrote:
I was running and rerunning a set of
functional tests. I was not stopping the app, but between each run I
would run a script to reset the data. Sigh. And part of the script,
Don't you use WOUnitTest? It helps setting up and tearing down
t
Am 24.02.2007 4:08 Uhr schrieb "Chuck Hill" unter
<[EMAIL PROTECTED]>:
> As it turns out, I am an idiot.
Well, I can't disprove this :-)
>I was running and rerunning a set of
> functional tests. I was not stopping the app, but between each run I
> would run a script to reset the data. Sigh. A
On Feb 23, 2007, at 10:08 PM, Chuck Hill wrote:
As it turns out, I am an idiot.
No.
Now, without a doubt, it is time for beer.
Yes.
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-
As it turns out, I am an idiot. I was running and rerunning a set of
functional tests. I was not stopping the app, but between each run I
would run a script to reset the data. Sigh. And part of the script,
which I have been watching scroll before my eyes and not reading, was
reseting th
On Feb 22, 2007, at 7:51 AM, Mike Schrag wrote:
I don't know that I am seeing snapshots invalidated. When this
happens, I can log out editingContext().committedSnapshotForObject
(eo) and see that the values are not null. But the snapshot that
the EODatabaseOperation gets is empty. At thi
I don't know that I am seeing snapshots invalidated. When this
happens, I can log out editingContext().committedSnapshotForObject
(eo) and see that the values are not null. But the snapshot that
the EODatabaseOperation gets is empty. At this point I am only
guessing at how that might be h
Hi Mike,
On Feb 21, 2007, at 5:54 PM, Mike Schrag wrote:
Every time I've ever seen this it's either 1) touching an unlocked
EC, 2) touching an unlocked EODatabaseContext (directly -- i.e. not
through a locked EC), or 3) you just straight up invalidated that
EO while something was in the mi
Every time I've ever seen this it's either 1) touching an unlocked
EC, 2) touching an unlocked EODatabaseContext (directly -- i.e. not
through a locked EC), or 3) you just straight up invalidated that EO
while something was in the middle of an update.
You can listen for the objectschangedin
Darn. That only "fixed" it in one batch of tests. I have another
that it still does this in.
Sigh. Ideas? Anyone?
Chuck
On Feb 21, 2007, at 3:04 PM, Chuck Hill wrote:
Hi,
Some of you will recognize this extremely fun exception:
java.lang.IllegalStateException: rowDiffsForAttributes:
Hi,
Some of you will recognize this extremely fun exception:
java.lang.IllegalStateException: rowDiffsForAttributes: snapshot in
com.webobjects.eoaccess.EODatabaseOperation {
_dbSnapshot = {};
...
this = "[DownloadLog (java.lang.Long)0]>"; }";
_globalID = _EOIntegralKeyGlobalID[DownloadLog (
10 matches
Mail list logo
