id summary reporter owner description type status priority milestone component version resolution keywords cc 104 'reference' tokens are occasionally broken Brian Warner "While investigating [http://allmydata.org/trac/tahoe/ticket/541 Tahoe#541], it seems to me that the 'reference' token is just plain broken. Specifically, the calls to {{{setObject}}} are showing up with counter values which don't match up. One test client did a remote call with the sequence: * OPEN(4) ""call"" 3 1 ""allocate_buckets"" OPEN(5) ""arguments"" 5 ""arg1"" ""arg2"" OPEN(6) ""set"" 1 CLOSE(6) ... and on the server side I saw setObject(5) called with a set, and no call to setObject(6). Something is screwy, it looks like somehow the counter value is corrupted or stale when it is passed in to setObject(). A quick glance suggests that setObject is being called at the right time and with the right objects, it's just that the counter= value is wrong (usually 1 smaller than it should be) " defect closed critical 0.4.0 banana 0.3.0 fixed