With the recent get next N changes (fromchange, tochange) in bug 1078209 pushed to stage, I can reproduce one scenario where the Repo doesn't reload when it should. To reproduce: o load m-i and filter by author, eg. https://email@example.com o scroll to the bottom and click on get|next 10 *twice o nb. ...there aren't any more resultsets with that author name anyway o click on the mozilla-inbound repo button at the top navbar to reload m-i Expected: All m-i pushes reload, with no filter. Observed: Nothing happens.
I think that has something to do with the "skipNextReload" param. It's not getting set back to false if there are no more items to load.
Comment on attachment 8614327 [details] [review] PR r+, with the indentation fix :-)
Commit pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/25baf8d2b3668d461a1efa1b871611b84ee89057 Bug 1169758 - reload repo after author filter + get next N