Skip to content
This repository has been archived by the owner on Jun 17, 2021. It is now read-only.

Latest commit

 

History

History
25 lines (13 loc) · 2.58 KB

changelog.md

File metadata and controls

25 lines (13 loc) · 2.58 KB
Raw

Changelog

2020-02-14

Updated the readme to illustrate how to change the Google account profile used by the application. I should have made this change with the previous update, but apparently didn't.

2018-12-30

As I made the changes in the previous release, I noticed that Google changed the way that the Python library initialized and authenticated with Google. The difference was slight, but the 'new' approach made more sense for my implementation of this, so I adjusted my program to use the new approach. Previously the code made a special folder for the API token it gets from Google on first setup, but the new approach just plunked the token file in the folder where the app runs (that made more sense to me).

The original project also installed Python libraries using sudo which isn't necessary. The python app executed using sudo as well, but that created some access problems I didn't want to have, so I reworked everything so it doesn't need sudo anywhere. That meant a slight change to the shell script that launches remind.py.

2018-12-22

Updated the Google Calendar API implementation - When I made the previous update, I noticed that the Google Calendar API getting started page had examples of a newer, cleaner approach to using the API. so, I decided to implement it.

2018-12-21

  • Added a reboot timer to remind.py. I noticed that when I lost power in the house, the PI would come up before my network did, and never reconnect. So, when you set REBOOT_COUNTER_ENABLED to True and specify a reboot counter in REBOOT_NUM_RETRIES (it defaults to 10), the app will count how many times the API fails to connect, then reboots the Pi.

    Right now, the code doesn't check for the type of error, so any failure in checking the Google Calendar will trigger the reboot counter. the right way to do this would be to figure out what all the possible errors are, and trigger this only for network errors. I've been running this app in my office fr years now, so I feel comfortable with the code the way it is.

  • Added a socket timeout to remind.py. As I started testing this code, I noticed that the big except I use to catch errors connecting to the Google Calendar API was hanging. A recent update to the Google API library, or something else on the Pi was causing this to fail now when it wasn't failing before, so I added the timeout to force the error.

  • Refactored the startup script start-remind.py. As I was testing the updates to the Python code, I realized that I wanted the shell script to show me which version of the python app it was running (by file date).