Dear Pamela, The test matrix is currently the following:
robot name notificaiton from arbitrary test wave access/edit large test wave* wavevotely yes no wavenotif no no wavearchive yes no arbitrary test wave used: https://wave.google.com/wave/#restored:wave:googlewave.com!w%252B3EnopNVcA large test wave used: https://wave.google.com/wave/#restored:wave:googlewave.com!w%252BfkhgC1biA Both waves were added to the [email protected] group. Results were evaluated by removing the robot, navigating to a distinct wave (for changeset commit), navigating back to wave, adding the robot, waiting 2 mins, and inspecting the access logs. Access log listing: https://appengine.google.com/logs?=&app_id=wavenotif&version_id=1c.337391612590976991&logs_form=1&severity_level=# http://appengine.google.com/logs?=&app_id=wavearchive&version_id=20.337376041243851173&logs_form=1&severity_level=# http://appengine.google.com/logs?app_id=wavevotely&version_id=8.337319959176843825&logs_form=1&severity_level=1# thank you for your speedy response, SDr On Fri, Oct 30, 2009 at 5:29 AM, pamela (Google Employee) < [email protected]> wrote: > Is this happening for all waves the robot is on, or just the long ones? > > There is a bug that affects all waves: > > http://code.google.com/p/google-wave-resources/issues/detail?id=278&q=label%3AApiType-Robots%20label%3AType-Defect&colspec=Stars%20ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%20Internal > > But if it's just wave-specific, then this seems like potentially a > different bug. > > - pamela > > > On Fri, Oct 30, 2009 at 4:27 PM, Silicon Dragon <[email protected]> wrote: > >> An official response for this issue (ack/deny) would be really appreciated >> >> Thank you, >> -SDr >> >> >> On Fri, Oct 30, 2009 at 2:41 AM, Silicon Dragon <[email protected]> wrote: >> >>> Hi, >>> >>> For several, content-rich waves with high number of editors, robots are >>> not receiving any notifications whatsoever. >>> Steps to reproduce: >>> >>> 1, open >>> https://wave.google.com/wave/#restored:wave:googlewave.com!w%252BfkhgC1biA >>> 2, add any robot listening to WAVELET_SELF_ADDED, or BLIP_SUBMITTED (for >>> simple example, see [email protected] ) >>> 3, observe logs ( >>> https://appengine.google.com/logs?=&app_id=wavenotif&version_id=1b.337357556183848162&logs_form=1&severity_level=1# >>> ) >>> >>> *Expected result*: Robot is notified for adding, and receives wave >>> content. >>> *Observed result*: No notification, or request from *WaveRobotGateway* * >>> whatsoever* >>> >>> (this is a show-stopper bug, for most of my robots assume to be called >>> for interaction) >>> >>> Looking forward to *any* solution, >>> SDr >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" 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/google-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
