normal pattern and "chopped" pattern share id, leading to possible FP
detect validation trusts mpm, but due to shared id match of pattern may actually be a partial match
Please also add a unit test to make sure a normal and a fp chop pattern won't get the same id.
- Due date set to 11/09/2012
- Priority changed from Normal to High
This hasn't been fixed in master yet, has it?
The temporary fix(disabling no inspection of content keywords that are mpm as well) is already applied to the master.
The shared id solution isn't in yet. Iirc it's waiting on a comment from you.
- Status changed from Assigned to Closed
- % Done changed from 0 to 100
Okay, closing. Wrt that comment, I have nothing in my inbox or elsewhere, so we should restart the conversation :)
Also available in: Atom