Hi Dave, I just reproduced your bug. Using your leap-year recurrence as the first insert of a batch(which the calendar server rejects), would stop the flow of processing for the entire batch. But when I moved this request to the end of the batch, the ones before it actually did got processed. This sounds like be a bug, it should process all the valid requests instead of returning 500 right away on the first invalid entry
Please file a bug for this, I will push it forward - http://code.google.com/p/gdata-issues/issues/entry Thanks! Austin On Thu, May 29, 2008 at 1:31 PM, Austin (Google) <[EMAIL PROTECTED]> wrote: > Hi Dave, > > It's possible that one error from one request within a batch of requests to > stop the processing of the others. Let me know test this out to verify, I > will get back to you on this. Thanks > > Austin > > > On Tue, May 27, 2008 at 8:13 PM, Dave <[EMAIL PROTECTED]> wrote: > >> >> No, I'm sending a whole bunch of events in the batch, and every single >> one fails. The first event in the batch is the leap-year bug event >> from this post >> >> >> http://groups.google.com/group/google-calendar-help-dataapi/browse_thread/thread/844eb9cd435fbd10 >> >> Is it possible for one error to taint the rest of the batch? >> >> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
