Hi Dave, Thanks for the information. If you have any more details on these problems with Search History and Blogger, please let me know and I'll get the information to the right people.
Meanwhile, we are working on solving this problem in Calendar. Thanks, -Ryan On 2/16/07, dave <[EMAIL PROTECTED]> wrote: > > > > FWIW I've been seeing this sporadic off-by-one-hour behavior also on > other Google services, most notably Search History and Blogger. > However the time error seen in those two services has been one hour > ahead instead of one hour behind as Kulvinder described. > -dave > > On Feb 15, 3:16 pm, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote: > > Hi Kulvinder, > > > > Thanks for the corroboration of the report. > > > > Yes, we have tracked down the bug and are working on resolving it. > > Unfortunately, it's not as simple of a fix as it sounds, so I can't give > any > > timeline for resolution. > > > > I'll post a note to the group when this is resolved. > > > > Thanks again, > > > > -Ryan > > > > On 2/15/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > > > > > Hi Ryan, > > > > > I also got this problem today morning. My Outlook and Google TimeZones > > > are both at GMT -5:00 EST. One of my Outlook Recurring event was at > > > 9:00 AM of duration 30 minutes. It was created in Google at 8:00 AM > > > instead. Other recurring events in the Outlook Calendar were at the > > > right time in Google. > > > > > When i updated my Oultook event and pushed in Google again, the wrong > > > event was shifted to right time. I think the time shiftin of -1 hour > > > occurs only while adding the events in Google calendar. > > > > > Any ideas ? > > > > > On Feb 9, 6:55 pm, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote: > > > > Hi Charlie, > > > > > > We are aware of and can reproduce the problem. We are working on > fixing > > > it, > > > > but unfortunately I can't give a timeframe. > > > > > > Thanks for the reminder. > > > > > > Cheers, > > > > -Ryan > > > > > > On 2/8/07, Charlie Wood <[EMAIL PROTECTED]> wrote: > > > > > > > Ryan, > > > > > > > I'm still seeing this behavior. Any news? > > > > > > > Thanks, > > > > > Charlie > > > > > > > On Jan 5, 10:51 am, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> > wrote: > > > > > > Hi Derek, > > > > > > > > We haen't found the exact cause yet, so I can only give you > guidance > > > > > > from my tests. > > > > > > > > With the given syntax, for doing a recurring even that repeats > daily > > > > > > for an indefinite period of time and lasts 60 minutes, I am able > to> > > > reproduce this with at least 4 different hours with the12312006 > > > start > > > > > > date and using the US Central timezone (America/Chicago). > > > > > > > > I was able to produce this on between 1 and 3 times out of 20 > > > requests > > > > > > in each batch run. > > > > > > > > I'll post to the groups when I have more information about this > bug. > > > > > > > > Cheers, > > > > > > > > -Ryan > > > > > > > > On Jan 4, 9:20 am, "Derek" <[EMAIL PROTECTED]> > wrote: > > > > > > > > > Thanks Ryan and Charlie. > > > > > > > > > I'd like to update our QA team to be aware of this issue, can > you > > > > > > > provide any guidance regarding what factors are involved in > the > > > > > > > manifestation of these recurrence issues? > > > > > > > > > Any and all recurring events, specific TZ/times... > > > > > > > > > Thanks in advance, > > > > > > > Derek.http://www.calgoo.com > > > > > > > > > Ryan Boyd (Google) wrote: > > > > > > > > I think I accidently hit 'Reply to author' on this one. > > > > > > > > > > I have been able to successfully recreate this issue -- > thanks > > > to > > > > > > > > Charlie and all the information he provided. > > > > > > > > > > While we will work to resolve this issue on our side, I did > > > notice > > > > > > > > during my testing that there is a way for the client to > check > > > > > whether > > > > > > > > the event was properly created. The gd:recurrence element > in > > > the > > > > > > > > response does include an incorrect value for those times > when > > > the > > > > > time > > > > > > > > for the event is offset. > > > > > > > > > > For instance, after submitting the following: > > > > > > > > DTSTART;TZID=America/Chicago:20061231T080000 > > > > > > > > the following was returned: > > > > > > > > DTSTART;TZID=America/Chicago:20061231T070000 > > > > > > > > > > If you wish to handle this issue before the bug is resolved, > you > > > > > could > > > > > > > > look at the resulting gd:recurrence element and edit the > event > > > if > > > > > > > > necessary. > > > > > > > > > > Thanks again Charlie. > > > > > > > > > > Cheers, > > > > > > > > > > -Ryan- Hide quoted text - > > > > > > - Show quoted text - > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar Data 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-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
