Validate scan attributes returned by participants
Reported by Ben Hood | July 14th, 2011 @ 10:19 AM | in 0.9-series (closed)
Currently we don't do any validation of the attributes in a ScanResultEntry as returned by a participant. These need to get checked for nullness/emptiness as well as making sure that it is compatible with the categories that are configured on the pair. The same validation needs to be performed for events ingested into the Changes frontend as well.
Comments and changes to this ticket
-
Ben Hood October 13th, 2011 @ 01:19 AM
(from [b9197d5bb3343added8b2b23fd3dcd007b68f59d]) [#292] Ensure that received scan results and realtime results are valid.
The aim is to ensure that we don't accept data that will produce strange results from participants, instead
erring on the side of validating before we store.
https://github.com/lshift/diffa/commit/b9197d5bb3343added8b2b23fd3d... -
Ben Hood October 13th, 2011 @ 01:37 AM
(from [6b5e4354df8a79c9df61d75bad79c2c4fc59ee8c]) [#292] Add integration tests for ignoring entities.
Upgrade messages from debug to warn to make them appear in logs.
https://github.com/lshift/diffa/commit/6b5e4354df8a79c9df61d75bad79... -
Paul Jones October 13th, 2011 @ 01:58 AM
- State changed from “new” to “resolved”
- Assigned user set to “Ben Hood”
Ready for QA
-
-
Ben Hood November 14th, 2011 @ 05:35 PM
- Milestone set to “0.9-series”
- Milestone order changed from “14” to “0”
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