-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KeyError: 'summary' #6
Comments
Well the 'summary' field is supposed to contain the event name, do you have any Google calendar events that don't have a name/title set? You can try adding a If it is just as simple as some of the Google events not having names then I can modify the script to fix that... the 'name' lookup isn't actually being used for anything much in that block of code anyway. |
Oh, yeh, i was testing in gcal and made an event without a name
It deleted it but did not empty the trash
Thanks
Adam
…On Thu, Oct 31, 2019 at 1:14 PM Andrew Ramsay ***@***.***> wrote:
Well the 'summary' field is supposed to contain the event name, do you
have any Google calendar events that don't have a name/title set? You can
try adding a print(gcal_event) on the previous line to see what's
actually contained in each gcal_event object.
If it is just as simple as some of the Google events not having names then
I can modify the script to fix that... the 'name' lookup isn't actually
being used for anything much in that block of code anyway.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6?email_source=notifications&email_token=ABKXAE7BXXBAXBX456D6EPDQRLKZ5A5CNFSM4JHJALR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECXW6UI#issuecomment-548368209>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKXAE3VO645NRYN5K4IM33QRLKZ5ANCNFSM4JHJALRQ>
.
--
Adam Barnett
|
OK, I'll add a quick fix for this in case anyone else runs into the same problem. |
should be fixed in d5a6865 |
Hi,
I have started to get this error
How can i trace back what is causing it
The text was updated successfully, but these errors were encountered: