I think I found a bug in Acumatica in EPTaskEnq graph

I am overriding the PXSelect in the EPTaskEnq graph.  After beating my head on the wall for an hour thinking my overridden select statement was causing an error, I simply copy/pasted the ORIGINAL select statement into my code. this is the definition of the Tasks view on EP404000.

        [PXFilterable]
        [PXViewDetailsButton(typeof(CRActivity), OnClosingPopup = PXSpecialButtonType.Refresh)]
        public PXSelectReadonly2<CRActivity, 
            LeftJoin<EPView,
                On<EPView.noteID, Equal<CRActivity.noteID>,
                And<EPView.contactID, Equal<Current<AccessInfo.contactID>>>>,
            LeftJoin<CRReminder,
                On<CRReminder.refNoteID, Equal<CRActivity.noteID>>>>,
                Where<CRActivity.classID, Equal<CRActivityClass.task>, And<
                    Where<CRActivity.workgroupID, IsWorkgroupOrSubgroupOfContact<CurrentValue<AccessInfo.contactID>>,
                        Or2<Where<CRActivity.workgroupID, IsNull, And<CRActivity.ownerID, IsSubordinateOfContact<CurrentValue<AccessInfo.contactID>>>>,
                        Or<CRActivity.ownerID, Equal<Current<AccessInfo.contactID>>,
                        Or<CRActivity.createdByID, Equal<Current<AccessInfo.contactID>>>>>>>>, 
            OrderBy<Asc<CRActivity.endDate,
            Desc<CRActivity.priority,
            Asc<CRActivity.startDate>>>>>
            Tasks;

This graph extension, causes an error and I think I know why.

In the Where clause, you see this particular line:

Or<CRActivity.createdByID, Equal<Current<AccessInfo.contactID>

createdByID is type GUID and contactID is type int

My confusion is that if there is an error in the code repository, does that mean that the code repository is incorrect BUT the actual code Acumatica is using is correct?  Is the code repository just a “copy” of code that we can refer to???  

I don’t want to report any bugs to Acumatica unless it is really a bug.  Also, what is the correct value to fix the bad line?  Should I report this as a bug and ask for the real definition of the View if this is indeed an error?