Imported waves are not found in my inbox [Google Apps account]

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Login to my personal walkaround instance with my Google Apps account login.
2. Go to the import page (http://localhost:8080/import) and click on the "Find 
waves to import" button under "Find waves to import manually", selecting 
"googlewave.com".
3. For several of the waves, click on the "shared import" button.
4. After each wave is confirmed to be "imported", check the inbox and find out 
that none of the imported waves are listed there.
5. Going back to the import page and clicking on the "imported" link for each 
wave displays that they have been imported onto my system.

What is the expected output?  What do you see instead?
I expected to see each wave which I was a participant (in Googlewave) in my 
walkaround inbox.  Instead, I only see the waves that I created in walkaround.

What browser and browser version are you using?  On what operating system?
Google Chrome 16.0.912.77

What URL does your browser show when the problem occurs?  Did you compile 
walkaround on your machine, or are you using a public instance?
http://localhost:8080/inbox
walkaround was compiled on my local machine.

Please provide any additional information below.
Installed Debian 6.0.4 (Squeeze). Setup participant avatars; modified the 
runant script as explained in the RunningTheCode webpage. Have not yet deployed 
walkaround to App Engine.

Original issue reported on code.google.com by RichieK...@gmail.com on 10 Feb 2012 at 12:33

[GoogleCodeExporter]

If you are using the master branch (not full-text-search), this is expected.  
Imported waves will only show in your inbox if you modify them.

Original comment by oh...@google.com on 10 Feb 2012 at 8:28

[GoogleCodeExporter]

Looks like I followed the Getting Started instructions in the wiki and ran into 
this issue as well.  I'm guessing that we need to check out and deploy a 
special branch, rebuild the indexes, re-link it to our account, somehow see 
archived waves, or something else I can't just make up with the little 
knowledge I have?  I'd rather not have to go through and open every wave just 
to make random changes to each one...

Original comment by eri...@teamworkgroup.com on 25 Mar 2012 at 5:40

[GoogleCodeExporter]

What is your goal?  If you want to see a list of all your imported waves, you 
can do so at /import .

Original comment by oh...@google.com on 26 Mar 2012 at 10:10

[GoogleCodeExporter]

Is this a stable "folder" to see the list of all waves you cannot see through 
the normal interface?  It appears to depend on availability of remote servers 
for its list of available waves (or the "delete everything" button wouldn't be 
so prominent).  If the link is broken with the remote server, would the waves 
be accessible from any other location (outside of /import) or would they be 
effectively subject to garbage collection?

This is starting to sound like it might be tied to a feature request likely 
found elsewhere for folders, in which case all the imported entries could be 
attached to "something other than the inbox".  I was really expecting to see 
them land "unread in my inbox" rather than only available in the import screen 
(with every wave back-dated  to 12/31/1969)

Original comment by eri...@teamworkgroup.com on 26 Mar 2012 at 10:16

[GoogleCodeExporter]

/import will keep its list regardless of the availability of remote servers.  
It deletes the list only if you click "forget all remote waves", so don't do 
that.  Even if you click it, your waves will still be there, but they will be 
impossible to find unless you remember their IDs or until you upgrade to the 
full-text-search branch and re-index all waves.

Waves only become subject to garbage collection if you remove yourself as a 
participant.

Original comment by oh...@google.com on 26 Mar 2012 at 10:30

[GoogleCodeExporter]

It sounds like full-text-search might be at least a workaround for me (not sure 
about the OP).  I'm assuming this is a git branch and I can use the 
instructions on RunningTheCode ("./deploy" followed by "update_indexes 
build/war" perhaps) to integrate the imports without having to re-import them?  
Is full-text-search running too far beyond trunk and/or is it stable for me to 
be running?

Original comment by eri...@teamworkgroup.com on 26 Mar 2012 at 10:37

[GoogleCodeExporter]

The full-text-search branch is about as stable as the rest of walkaround.  You 
can find the list of known bugs in this bug tracker.

See 
https://groups.google.com/group/walkaround-dev/browse_thread/thread/2dc3527f6ff2
1119?pli=1 and in particular 
https://groups.google.com/group/walkaround-dev/msg/dcfefe1aca0dd0c6 for 
information on how to get it running, and how to build the full-text search 
index.

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

[GoogleCodeExporter]

Looks like everything is working as intended here.  Behavior is a bit odd on 
the master branch but not worth fixing since the full-text-search branch is the 
way forward.  Feature request for folders should be a separate issue.

Original comment by oh...@google.com on 3 Apr 2012 at 6:38

• Changed state: WontFix