whisper out of range time range cause incorrect value to be returned

Bug #1111285 reported by Sébastien Bernard on 2013-01-31
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
whisper
New
Undecided
Unassigned

Bug Description

When specifying a range in the future, fetch_file accepts the range as ok and returns an incorrect timeinfo with an end < start.

How to reproduce :
take any timeseries
Call fetch_file with
   from = now + 1h
   until = now + 3h

fetch_file returns a series of NONE values correct with a timeinfo like this:

  start = from
  end = now

As from is in the future, the timeinfo returned has end < start which is cleary a bug.

affects: graphite → whisper
Sébastien Bernard (sbernard) wrote :

By the way, this bug affects the 0.9.10 version of whisper and cause error 500 at graphite dashboard.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers