Possible bug in batch duration calculation: duration can be longer than the render that's observed in the timeline

[taneliang]

From #123:

I suspect there's a bug in our batch duration calculation, because the zoom to method often zooms to an empty space. This is not a bug in the zooming: the view is zoomed to a range that matches the batch duration displayed in the tooltip.

Perhaps caused by the lack of render cancelled marks (MLH-Fellowship/react#30)?

Update 19 Aug

Seems like getBatchRange just sets the range's end time to the start time of the next batch. Is this intentional/correct?

scheduling-profiler-prototype/src/utils/getBatchRange.js

Lines 29 to 35 in 95b2154

	for (i; i < measures.length; i++) {
	const measure = measures[i];
	stopTime = measure.timestamp;
	if (measure.batchUID !== batchUID) {
	break;
	}
	}