Stale=false doesn't return latest data in some scenarios

[adamcfraser]

Moved from couchbase/sync_gateway#1951:

My understanding of the purpose of having the stale=false option on view queries was to ensure that the view was up to date with documents already added, allowing the possibility of "read your own writes" for such indexed queries. Is this correct? If so then it sometimes fails.

It seems that if a view is queried before an insert into the database then a subsequent query of the view can fail.

I have isolated the problem in a test:

Steps to reproduce here:
https://gist.github.com/paulharter/e33422b1f7d20de462f8b48e07f10310

[jamescooke]

This is a pretty old issue and I've run into it (again) today but forgot that Walrus doesn't handle the undocumented stale=false view param. Is there any new info on what scenarios do mean that Walrus gives a non-stale view? - I haven't been able to find any.

The reason I'm asking is because I want to test an integration that depends on fresh view data. Our test suite runs on Walrus - for one of our tests it creates new entries and then queries them back via a view with stale=false but that never gets the new entries as a result of this issue.