{"push_id":2580266225,"size":3,"distinct_size":3,"ref":"refs/heads/v4.0","head":"9001ec3686d3d465cd38b395e7e506b159d2a2c4","before":"e65d35b2f40aa462908fe8b1be4636a88b95a4e5","commits":[{"sha":"536eb2dcc79600d36d016177393d5bfd3a3dbffe","author":{"name":"Arkadiusz Palinski","email":"b92f94d179fae96e46b2950d8ced1c17a099c0bd@ravendb.net"},"message":"RavenDB-11153 When the last queried index was auto one and we don't have any other to calculate the time difference (used in idle index detection mechanism) then use the difference between last query time and now but only if the index was queries _after_ database start (we need to prevent from marking an auto index as idle immediately after db restore or restart). Fixing test.","distinct":true,"url":"https://api.github.com/repos/ravendb/ravendb/commits/536eb2dcc79600d36d016177393d5bfd3a3dbffe"},{"sha":"ee9b18b32637dae2b87960b9180d6361d1b52d3d","author":{"name":"Arkadiusz Palinski","email":"b92f94d179fae96e46b2950d8ced1c17a099c0bd@ravendb.net"},"message":"RavenDB-11159 Include index state in the index etag value so we'll be sure that cached queries will get invalidated if the index state has changed meanwhile. In particular it fixes the case that an auto index won't switch its state from idle to normal even if it gets new queries. Ensure we won't fail a query or idle operation task when we fail to set index state, e.g. due to voron tx timeout, if huge indexing batch is running.","distinct":true,"url":"https://api.github.com/repos/ravendb/ravendb/commits/ee9b18b32637dae2b87960b9180d6361d1b52d3d"},{"sha":"9001ec3686d3d465cd38b395e7e506b159d2a2c4","author":{"name":"Ayende Rahien","email":"72c47a07e3ac029696b4eff8a030dc2eb2263e95@ayende.com"},"message":"Merge pull request #6238 from arekpalinski/RavenDB-11153\n\n[4.0] RavenDB-11153 and  RavenDB-11159","distinct":true,"url":"https://api.github.com/repos/ravendb/ravendb/commits/9001ec3686d3d465cd38b395e7e506b159d2a2c4"}]}
{"actor":{"display_login":"ayende"}}