Handle null lastUpdated field from participant
Reported by Ben Hood | July 13th, 2011 @ 09:38 PM
Currently Diffa does not methodologically choose whether the lastUpdated field in a ScanEntry is a mandatory field or not. Changeset 7a6b94235ca9fe6a83ee addressed this shortcoming by avoiding a NPE, but it didn't decide whether this is the intended behavior. Hence we need to finalize what the mandatory wire parameters are and accommodate accordingly.
Comments and changes to this ticket
-
Ben Hood July 14th, 2011 @ 10:14 AM
- State changed from “new” to “closed”
This was fixed in f2c83b30dcac47edcbbb => closing
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Ben Hood