Import does not work for non-GMail Google Accounts about walkaround HOT 14 CLOSED

What URL does your browser show when the problem occurs?  Did you compile 
walkaround on your machine, or are you using a public instance?

Are you an explicit participant on the waves you tried importing, or do you 
have access because the wave is public, or through a googlegroups group?  I 
think import currently only works if you are an explicit participant.

I'm using the public instance, so the URL is 
https://wavereactor.appspot.com/import
This URL remains the same before & after clicking the Import button.
The first wave I tried importing, I created myself and there are no other 
participants.  The other is one where I was an explicit participant (I have 
almost no public waves in my inbox).

Thanks for the quick response.  Is there any other information I can provide to 
help?

I've never seen this before, but importing hasn't been tested much yet, so 
that's no surprise.  If the task pops off the list, that means it's considered 
successful.  I'll be spending some more time on the import feature soon, so it 
would be good to know more about what you're seeing.

Are you using walkaround with an @gmail.com address or your own Google Apps 
domain?

Can you try running your own instance to do the import so that we can see the 
server logs?

I'm not using Google Apps, just my standard Google Account (linked to a 
non-gmail email address).  I found one wave when I try to import it would get 
"stuck" and stay on the list - I left it 24 hours befor ecancelling it.

I have no idea what language Walkaround is, and I'm really not a web developer, 
but I'll see if I can get my own instance up and running and if so, come back 
to you with logs.  Out of town this weekend so hopefully I can check it out 
next week sometime.

Cheers

Ah, a Google account linked to a non-gmail email address.  That is indeed a 
case we haven't considered.

Does the address that walkaround's inbox shows in the top right match your 
address in Google Wave?  Or do you have an @googlewave.com address that 
corresponds to an @gmail.com address that you don't use?  Can you log in to 
walkaround as that @gmail.com address and try the import?

The address in Walkaround's top-right corner is my personal email address 
(which doubles as my Google username, that I use to login to wave).  This is 
what corresponds to my @googlewave.com address.

There is no GMail product associated with my Google account.  Just to make that 
really clear if I navigate to google.com and then in the top-right bar (since 
I'm already logged in) open "Account settings", GMail is not listed under the 
"My Products" section, but is listed under the "Try Something New" section - 
indicating that I don't have it but could add it to my account.

Since there is no GMail account, I cannot login to Walkaround with anything 
other than my normal Google username/non-GMail email address.  I'd rather not 
create a gmail account just to import my waves if at all possible please (:

I may be able to look into this some time in the next few weeks, but I think it 
will be much faster and less effort for you to create a GMail account.  I don't 
know if it will help, but it seems like a very easy thing for you to try.  Do 
you know if there's a way to deactivate the GMail account once you no longer 
need it?

(I wonder if this is related to 
https://groups.google.com/forum/#!topic/walkaround-dev/FsSzYqSh5rY .)

I think 
http://code.google.com/p/walkaround/source/detail?r=e606b3e76e0cc989d164094a1c6b
f77367e693ab may have fixed this.  Can you run your own instance to test?

Hi Christian,

Sorry for the silence recently.  Busy time.  That forum topic sounds very 
similar doesn't it?  Apparently a GMail account can be deactivated, but I've 
yet to try that option.

I've got GIT and pulled down the source, but I think building that is beyond my 
abilities at the moment I'm afraid - I wouldn't have a clue where to start now! 
):
If its not too extensive, can you point me to some kind guide?  Or is it 
possible to deploy your fix on the public instance by chance?

Thanks

https://code.google.com/p/walkaround/wiki/RunningTheCode describes how to build 
and run walkaround.  Unfortunately, I don't know if any of the public demo 
instances have this fix, since I am not an administrator on any of them.

Just an update, I tried to build the other day following these instructions 
however the get 3rd party dependencies failed with a bunch of errors, I think 
because I didn't have wget installed.  I found the source for that, but I 
couldn't build it either, ha ha.

However more importantly, I just tested import again on public instance 
https://walk-test.appspot.com/ and it appears to be working a bit better now.  
Following the same steps I listed in my first post, I now get the expected 
output of returning to my inbox and finding the imported wave there.  Returning 
to the /import URL however does still show the imported wave with a status of 
"?" and no link provided (I would have expected it to have a link to the wave 
in my inbox, and a status of "imported" or something?)

So it seems your fix has been deployed on this public instance, and that it has 
resolved the issue of not having a gmail email address with which to do the 
import.  Thanks very much Christian!

Great to hear this works now.  /import now also shows which waves have been 
imported, and I'm working on making "shared import" work to fix issues 2 and 41.

I just signed into the https://wavereactor.appspot.com/ instance again and 
checked my imported waves.  I noticed that the creator username is wrong.  What 
it has done is taken my Google wave address, dropped the @googlewave.com and 
replaced it with @gmail.com, which is completely wrong since as I said already, 
I don't have a gmail account.

This is a problem of mapping from Wave usernames to Google account usernames.  
I've been talking to the guys at Rizzoma and it they are facing the same 
problem.  Because they use the waveshortcuts browser plugin, they can 
technically read the current user's wave address from the contacts panel of the 
page, and use that to do the mapping *for your own user only* - it would be 
impossible to map any other users, but  at least it would be an improvement.

I don't know if you have any other ideas for a solution to solve this problem?