Downsampling a range into a single value gives unexpected results about heroic HOT 5 CLOSED

Hey!

The first thing I can think of is that a feature called com.spotify.heroic.shift_range is enabled by default.
This causes the range that you are querying for to be shifted according to your cadence (341s), so the queried for range would be rounded to 341 seconds.

You can try to disable this feature, and see if things make more sense by adding the following to your query:

{
  "features": [
    "-com.spotify.heroic.shift_range"
  ]
}

The actual queried for range should be included in the result, see if it matches up with what you provided.

Please tell me if it still doesn't make sense.

from heroic.

Agreed, it's a fairly recent addition.
I've added #134 to track this.

from heroic.

That seemed to solve it, thanks for your quick reply!

If this is an undocumented feature it might be a good idea to add a note about it in the docs :)

from heroic.

@hampusohlsson Feature flags have now been documented a bit as per #134, please have a look to see if its satisfactory. Thank you for your feedback.

from heroic.

Looks good 👍

from heroic.