Still happening on Chrome 3.0.183.1

It happens on any wave that I send between me and my test account.  And these waves
that have no content can not be deleted.

Same here re: between me and my -test account. I'm not enough of a masochist fangrrl to 
start coding anything until this is resolved. If I did something wron I'll be glad to 
fix it, but my clue queue is empty.  

I'm getting this for the "public waves" wave. Wave has no contents. Consult backend 
logs for wave id wavesandbox.com$w+AzErvK2w%4

 	
		
Chris Fullmer   	
View profile  
Hi. I've had another thread about this, but it got washed away with all the other
great threads.  And I was asked to post my problem so that others who might be having
the same problem can find a solution (which would suggest there is a solution and
someone is planning on posting it?) Every wave that I try to send between my main
account and my test account is corrupt.  This is what I get as the contents of the
wave: Wave has no contents. Consult backend logs for wave id wavesandbox.com
$w+gdzQ6H3A%0 (but the waveID differs on each of the waves).  I have joined and
started other waves with no problems. The wave does go through from account to the
other.  It makes it as far as the inbox.  I can even see the other account typing the
message in the inbox wave. But when I then click on the wave to open it, I get the
error above that the wave is empty. I have 2 of these waves in my main account WILL
NOT BE DELETED.  Not by "archiving" them or by moving them to the trash folder.  One
is near the bottom of my inbox and the other is the top wave in my inbox at all
times.  It says it has 3 new messages in it, but when I click on it, it gives me the
no content error. My test account also has about 4 of these waves that won't delete.
I'm wondering if it is possible that these corrup waves are somehow blocking my
communications between my 2 accounts? Any insight as to how to fix this would be
great.  Hopefully it will help others if they are having similar issues :) Chris Fullmer
	 More options Jun 5, 12:28 pm
From: Chris Fullmer <fullmer.fam...@gmail.com>
Date: Fri, 5 Jun 2009 09:28:19 -0700 (PDT)
Local: Fri, Jun 5 2009 12:28 pm
Subject: All waves between my main account and test account "Contain no contents"
Reply | Reply to author | Forward | Print | Individual message | Show original |
Report this message | Find messages by this author
Hi. I've had another thread about this, but it got washed away with
all the other great threads.  And I was asked to post my problem so
that others who might be having the same problem can find a solution
(which would suggest there is a solution and someone is planning on
posting it?)

Every wave that I try to send between my main account and my test
account is corrupt.  This is what I get as the contents of the wave:

Wave has no contents. Consult backend logs for wave id wavesandbox.com
$w+gdzQ6H3A%0

(but the waveID differs on each of the waves).  I have joined and
started other waves with no problems.

The wave does go through from account to the other.  It makes it as
far as the inbox.  I can even see the other account typing the message
in the inbox wave. But when I then click on the wave to open it, I get
the error above that the wave is empty.

I have 2 of these waves in my main account WILL NOT BE DELETED.  Not
by "archiving" them or by moving them to the trash folder.  One is
near the bottom of my inbox and the other is the top wave in my inbox
at all times.  It says it has 3 new messages in it, but when I click
on it, it gives me the no content error.

My test account also has about 4 of these waves that won't delete.
I'm wondering if it is possible that these corrup waves are somehow
blocking my communications between my 2 accounts?

Any insight as to how to fix this would be great.  Hopefully it will
help others if they are having similar issues :)

Chris Fullmer 

same issue here...

Thanks for taking the time to report these issues. I suspect there are several 
individual problems underlying the same symptom. It would help a lot if you were able 
to give explicit permission to Google Engineers to look at the content of the waves 
having problems.

Would each of you mind adding a note saying it's ok for us to see the waves, and 
their history, along with the wave ids you'd like us to be able to investigate? Also, 
if you could add captainal@wavesandbox.com to the broken waves, that would be helpful 
(though I guess it depends how broken the waves are, as to whether you can.)

Thanks!

Alan.

Adding Chris Fullmer's helpful video: http://chrisfullmer.com/chrisfullmer/forums/wave_problems.swf

Sure, anybody at Google has permission to look at any of my Waves to help solve this
problem. I'll add captainal to all my waves too. Bear in mind I'm also seeing this
problem on Waves I do not own, so I can't help with permissions there. Give me a
minute to get in there...

Chris: your video was a good insight into how real people actually think about wave. 
Here's some things that might be helpful in future, though I'm not sure it helps 
right now:

1. Waves aren't sent between accounts, there's a single, shared object that both 
accounts have - or are supposed to have - access to.

2. The timestamps are last modified timestamps, rather than creation timestamps. Are 
they accurate, taking that into account?

3. The "wave has no contents" message usually appears when there is a reference to a 
wave in your index, but the view server is unable to serve a view of the wave when it 
is opened. Sometimes this is because of a transient view server or wave server 
problem, in which case everything ought to be fine an hour or two later. Sometimes it 
is due to corruption of the wave, or a bug in the handling of the operation stream. 
This is the bug we need to resolve.

4. Because the view server wasn't providing access to the waves, you won't be able to 
do anything to them, including adding new participants or moving it out of your 
inbox.

If you don't mind, could you please make two waves, one started from each of your 
accounts, and add "captainal@wavesandbox.com". Please put " Issue 20 " in the title, so 
I can find them.

Hi Allan, thanks for looking into this.  

Yes, Google has my permission to look at these waves.  I can post each ID if 
necessary.  I will do it gladly! :)

I can't add anyone to the existing corrupt waves, and there are a few that are days 
old.  And the one that says its from 2:24...that timestamp is wrong.  It was from 
2:24 a few days ago, but has not been modified since it was created.  

But I will create a wave from each account, include the other account and the 
captain!  Hopefully that will help track it down.  Thanks you so much for responding,

Chris

The failure for me has been consistent: any wave that has this problem *always* has
it. So there are public waves I've never seen. 

As of today, I'm starting to see browser crashes (only with a Wave page up) too, in
both Chrome and Firefox. Even when just sitting with the WaveFAQ up, not touching
anything.    

As promised (threatened?) I will post the Wave ID for each of my broken waves, and 
maybe their life story too :)

These are in my TEST account:
wavesandbox.com$w+C4E87z6S%3 - Originated in my main account
wavesandbox.com$w+J3PId0R0%1 - same
wavesandbox.com$w+nc9ccIOi%0 - same
wavesandbox.com$w+Rawd7W97%0 - same
wavesandbox.com$w+1xZ_xINR%1 - same
wavesandbox.com$w+4Kh-OlyF%0 - same - This one includes the captain also
wavesandbox.com$w+dUDbR0sX%0 - this is the one I did in the video I'll link to


These are in my MAIN account:
wavesandbox.com$w+nC5-4QPd%0 - originated from my test account
wavesandbox.com$w+Q-RqDrC6%0 - same - I've included that captain on this wave
wavesandbox.com$w+EiwkThFb%0 - originated from another user
wavesandbox.com$w+gdzQ6H3A%0 - originated from my test account and stays at the top 
of my inbox even though it is a few days old.

Hopefully that helps.  And again, for me the corrupt waves are only a nuisance.  The 
real killer is that I can not share waves between my two accounts.  And I'm hoping 
these corrupt waves will help solve that issue.  Thanks!

And here is a video that shows it in action. sorry its large on the screen (only 
3.9mb though) 

http://www.chrisfullmer.com/chrisfullmer/forums/issues20tracker1.mp4

Chris

maggiel-test still can't open the wave created by maggiel titled "Hey, Siobhan!".

 Wave has no contents. Consult backend logs for wave id 
[WaveId:wavesandbox.com!w+RGV_2w3h%1]

I did notice that the detailed failure sequence is: the second user clicks once on the 
Wave, the Wave is highlighted there, and nothing happens. The Dr. Wave message doesn't 
happen until the second click, and then the "no contents" message is displayed. 

I wonder if the fact that contact search is broken and you can create a totally bogus 
contact is part of what's going on here? Allowing you to end up with a Wave carrying a 
participant tag that matches on a real participant only some of the time? Case-
sensitive vs. case insensitive matching?  

Although how I get "public waves" I cant open I don't know... I *can* openall if teh 
original set of welcomewaves

I was also thinking along those lines Margaret.  In the very beginning, I had used 
incorrect addresses when trying to add my accounts to eachother's contact list.  It 
is soo easy to do that using the search for contacts feature as it works right now.  
So I'm sure some of my corrupt waves include bogus addresses.  Here is a video which 
shows just how easy it is to create bad contacts.  I passed this on to Captain Al 
last night, and I should post it here so everyone can see it.

http://chrisfullmer.com/chrisfullmer/forums/add_contacts_incorrectly.mp4

Chris

comment 15 should end "I *can* open all of the original set of welcomewaves."

Chris and I had a long debugging/chat session about this issue. We suspect it may have 
to do with the fact that you can create *any* contact, even a close match that varies 
only in capitalization. I suspect that when this happens, a Wave can appear in your 
inbox because of a close match on your username, but then fail to be displayed because 
the match is not exact. I've been trying to link the wave to the FAQ, but both my 
browsers (Firefox and Chrome) are crashing before I get that far. The title is "Glad 
someone is still pushing to get the corrupt wave issue fixed up." and wave-discuss and 
Captain Al have been added to it

Just did a test between MaggieL and MaggieL-test...no joy. 

Maggie, check our wave, I found a fix!

Quoted from the wave:
HEEYYYY!!!!!!!!  I got my accounts to work with eachother and it is totally all about 
the capital letters!

So the original email told me my account was Chris.Fullmer@wavesandbox.com  So I 
logged in as Chris.Fullmer and Chris.Fullmer-test as my test account.

BUT wave is expecting all lowercase letters in the @wavesandbox addresses.  

So now, I deleted my contacts from each of my accounts.  Then re-added and used only 
lowercase letters.  Then I logged in to each account using lowercase letters:

chris.fullmer and chris.fullmer-test and Voi-la!  Suddenly my accounts communicate 
back and forth as expected.  phew!  I'll post this on the groups and also in  issue 24  
where I had brought this up.

Got it. I've started a Wave with the other developers and I'm hoping we'll have some
fixes for the next releases. This is a complex problem, so your patience is appreciated.

Meanwhile, please check that your contacts contain all lower-case letters. e.g
maggiel@wavesandbox.com, and not MaggieL@wavesandbox.com.
 

I've been testing some more and it appears that it might just be the capital letters 
I had used when I added my contact info to each account.  So my email I was sent said 
my accounts names were:

Chris.Fullmer@wavesandbox.com
Chris.Fullmer-test@wavesandbox.com

So I copied and pasted those into my contacts, or later typed thm in manually, exactl 
as written.  But it does indeed need lowercase letters.

I can confirm that it appears to not matter how I log in though.  I can log in as 
Chris.Fullmer or chris.fullmer and both work, now that I have the correct contact 
info for each account entered.

So it should be that corrupt waves appear corrupt if they are sent to Chris.Fullmer 
instead of chris.fullmer.  So if someone has copied and pasted my info from the group 
where I posted my address with capital letters, then when they wave me, it will 
appear corrupt.

So like alan notes in the comment above, make sure all contacts use lower case.  That 
seems to have solved it all on my end.

Maggie, can you confirm if that fixes it for you?

Bingo! I had tested with the presumption that how it was sent out in the welcome 
email was correct. 

----------
Login URL: https://wave.google.com/a/wavesandbox.com/
 Account Name: MaggieL@wavesandbox.com
 Password: xxxxxxxxx

We have also allocated you a second developer sandbox account, which you
may find useful for testing collaborative gadgets and robots.

 Account Name: MaggieL-test@wavesandbox.com
 Password: xxxxxxxxxxxxx (Same as your main account)
-----------

With the contact forced to all lower-case I'm now able to send back and forth. 

Now all I have to do is get somebody on each of the various "here's a list of 
everybody" waves to fix the places where my username is capped. :-) 

I've put together a fix for this which should hopefully make it to the build tomorrow. 
Sorry for any inconvenience and thank you all for finding and diagnosing this problem.

Thanks, Jon! your efforts are much appreciated.

I still have a few waves with "You are not a participant in this wave". 
None of them were originated by me:
!w%252BcP0Nd2rK%2525F
!w%252B1Q1tubgk%2525A
!w%252BJxzTnnS1%2525K
!w%252BoORon857%2525K
!w%252B18mjphgK%2525C
!w%252Bw7CrJXyP%2525A
!w%252BAz_N6WsC%2525A

I would appreciate if someone provided me with instructions how to remove those waves.

(No comment was entered for this change.)