>From your description it does sound like something is not working correctly, unfortunately it's not clear what. If you can reproduce the problem (e.g. are you sure you logged on to the client with the same username), we'd be interested in hearing the details. Please include information such as whether the wave is local or remote, the last time the server was restarted, a log dump of the client (/log), an excerpt of the server log with a particular waveletId. You can file a bug, ideally once you've made sure it's a reproducible bug (http://code.google.com/p/wave-protocol/issues/list). Thanks for your help :)
regards, Jochen On Tue, Nov 17, 2009 at 9:46 AM, Brian May <[email protected]> wrote: > > On Mon, Nov 16, 2009 at 02:37:49PM -0800, Tad Glines wrote: >> I've see this behavior in the past, but it seemed to be related to the >> server being in some weird state. In those cases, I had to restart the >> server. I wasn't able to replicate the problem, so I didn't try >> debugging it. > > Maybe I shouldn't have tried to test out all those old waves again, I might > have broken something by doing so. > > I guess I should restart my server, after applying updates, see what happens. > -- > Brian May <[email protected]> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
