Full-text-search indexing does not remove waves for removed participants

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. create wave
2. wait 1 minute until indexed
3. remove yourself
4. wait 1 minute for ACL cache to expire

What is the expected output?  What do you see instead?
Expected: Wave removed from inbox.
Actual: Wave remains in inbox but cannot be opened.

This is pretty bad because it makes it impossible to get rid of waves (e.g. 
imported waves that the user doesn't care about).

Having an archive feature could help as well.

What browser and browser version are you using?  On what operating system?
Chrome, Linux

What URL does your browser show when the problem occurs?  Did you compile
walkaround on your machine, or are you using a public instance?
deployed from full-text-search branch

Please use labels and text to provide additional information.

Original issue reported on code.google.com by oh...@google.com on 2 Feb 2012 at 10:45

GoogleCodeExporter commented 8 years ago

Original comment by oh...@google.com on 27 Mar 2012 at 7:25

Added labels: Priority-High
Removed labels: Priority-Medium

GoogleCodeExporter commented 8 years ago

Fixed by 
http://code.google.com/p/walkaround/source/detail?r=78911bd381a3b9594de322c86f8b
9b6fbc8aab41&name=full-text-search .

Original comment by oh...@google.com on 3 Apr 2012 at 5:45

Changed state: Fixed

mywhere / walkaround

Full-text-search indexing does not remove waves for removed participants #57