-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Bug: KeyError when The Event has no Summary Field #41
Comments
Isn't summary just the event name? how do you even create an event without a title? |
Are you sure? Can you reproduce it this way? Because I never enter a description and it doesn't crash for me |
Somehow I can't reproduce it now, but I am sure that's the problematic field since the error went away as soon as I put in some text there. (Previously, reinstalling did not help.) |
I read the logs you sent, seems like the error occurs in this line The summary field is the title as far as I know, this is how it works when I use it so there shouldn't be a different in your instance (unless there was a change to the API and you have a newer version than I) I'll look into the error when I get the time |
First. Thank you for this wonderful package. I just wanted to report that trying to install this with a fresh install through AUR i get a similar error. Credentials were created and look find. When I run with the -u flag I get.
I can see the .i3agenda folder is created, with the token.pickle. The .cache.txt file ends up being an empty array. If you have any ideas please let me know. This looks like a fantastic script and I appreciate the time you took to build it. |
🐛 Just tried this out and I have the same error as @snide. This looks like a fantastic module. <3 |
I looked into this and with patch in PR #48, the code no longer runs into this error. However I'm not sure if that's a complete fix. At the moment, after running the script just with the
|
Do you literally get "%d/%m"? or the actual day/month? I think maybe shared events really be the reason for this because I don't really have any shared events and I never ran into such issue |
@snide do you have shared events in your calendar? Could you try @indradhanush patch? |
Yes, indeed. I was confused and thought that maybe I am missing some additional configuration? I will try this out without a shared calendar and see if I am seeing a similar behaviour. |
I'll try to run the patch later today.
…On Fri, Feb 19, 2021, 3:56 AM Indradhanush Gupta ***@***.***> wrote:
Do you literally get "%d/%m"? or the actual day/month?
Yes, indeed. I was confused and thought that maybe I am missing some
additional configuration? I will try this out without a shared calendar and
see if I am seeing a similar behaviour.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#41 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACPHJ5VPQ7IRSI42HB7FY3S7ZGXJANCNFSM4QQEN6QQ>
.
|
I checked today where the next / current event description was publicly available from the shared calendar and the description along with the timestamp was printed as the output. However, if the event description is not publicly available, I still see the
Edit: My bad. I was reading the code, and it seems this is already doable with the |
Solved at #88 |
Looks like some commit broke it cuz it used to work for me on Manjaro i3. After adding a summary field, it works again.
The text was updated successfully, but these errors were encountered: