{"action":"opened","issue":{"url":"https://api.github.com/repos/graphaware/neo4j-timetree/issues/17","labels_url":"https://api.github.com/repos/graphaware/neo4j-timetree/issues/17/labels{/name}","comments_url":"https://api.github.com/repos/graphaware/neo4j-timetree/issues/17/comments","events_url":"https://api.github.com/repos/graphaware/neo4j-timetree/issues/17/events","html_url":"https://github.com/graphaware/neo4j-timetree/issues/17","id":58114690,"number":17,"title":"Unexpected monthly range behavior, not always inclusive","user":{"login":"subvertallchris","id":4097271,"avatar_url":"https://avatars.githubusercontent.com/u/4097271?v=3","gravatar_id":"","url":"https://api.github.com/users/subvertallchris","html_url":"https://github.com/subvertallchris","followers_url":"https://api.github.com/users/subvertallchris/followers","following_url":"https://api.github.com/users/subvertallchris/following{/other_user}","gists_url":"https://api.github.com/users/subvertallchris/gists{/gist_id}","starred_url":"https://api.github.com/users/subvertallchris/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/subvertallchris/subscriptions","organizations_url":"https://api.github.com/users/subvertallchris/orgs","repos_url":"https://api.github.com/users/subvertallchris/repos","events_url":"https://api.github.com/users/subvertallchris/events{/privacy}","received_events_url":"https://api.github.com/users/subvertallchris/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-18T19:23:44Z","updated_at":"2015-02-18T19:23:44Z","closed_at":null,"body":"If I want to get the TT nodes responsible for January and February, I thought I'd be able to give it two timestamps that fall within those months. So, January 31, 2015 and February 1, 2015:  http://localhost:7475/graphaware/timetree/range/1422662400000/1422748800000?resolution=month\r\n\r\nInstead, that returns January's node only. If I change it to give me Jan 31 - Feb 28, it still only returns January: http://localhost:7475/graphaware/timetree/range/1422662400000/1425081600000?resolution=month\r\n\r\nIf I bump it up to Jan 31 - March 1, it works: http://localhost:7475/graphaware/timetree/range/1422662400000/1425168000000?resolution=month\r\n\r\nIt seems like it wants a minimum of 30-ish days to trigger the query for the next month's time tree node, regardless of whether the timestamps themselves cross over months.\r\n\r\nYear does the same thing: a range from Dec 31, 2014 to Jan 1, 2015 only gives me the node for 2014. Jan 2, 2014 through Jan 1, 2015 ALSO does this, but if I switch it to Jan 1, 2014 - Jan 1, 2015, the problem goes away.\r\n\r\nAsking for a monthly resolution with a range of Jan 1, 2015 to Jan 15, 2015 gives January's node, so the above feels kind of inconsistent. I guess that it's finding the start of the range every time and if it doesn't cross a given time threshold based on the upper end, it doesn't move beyond where it started?\r\n\r\nFor now, we can work around it in the app by looking at the date range and resolution requested and bumping up the upper limit to force inclusivity. If this is by design, we'll live, but it feels somewhere between bug and undocumented behavior. Sincere apologies if this is already spelled out somewhere!"}}