Fix off by one date errors on CT reports

The utc conversion was causing it to cut off hours at the end of the
day as enddate would end up being a datetime object with 10pm today.
I'm confused why that's a bug. Is this if midnight somewhere happens to be
6pm utc, that's fine, right?
On Jun 23, 2014 6:38 PM, "Tyler Wymer" <notifications@github.com> wrote:

> In corehq/apps/reports/commtrack/standard.py:
>
> > @@ -138,8 +138,8 @@ def get_prod_data(self):
> >
> >          stock_states = StockState.objects.filter(
> >              case_id__in=sp_ids,
> > -            last_modified_date__lte=self.datespan.enddate_utc,
> > -            last_modified_date__gte=self.datespan.startdate_utc,
> > +            last_modified_date__lte=self.datespan.enddate_display,
> > +            last_modified_date__gte=self.datespan.startdate_display,
>
> The bug that this PR is addressing is that enddate_utc returns a datetime
> object that could, say, be 6pm today which then causes a bunch of data to
> not show up on reports.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/dimagi/commcare-hq/pull/3684/files#r14104305>.
>