Weekly Update - Monday, November 29th

[github-actions]

Copy and paste the template below, and answer questions as you wish!

Weekly Update

**Thanks I'd like to give 🙌**
- So-and-so helped me out a lot with XXX...
- Thanks for Jo's work on the XXX repo...

**Updates from last week ✔**
- I worked towards deliverable: <link-to-deliverable>
- I had a meeting with ABC

**Challenges I faced and things I'd like assistance with 🙏**
- I had a hard time figuring out ...
- Could somebody take a look at ...

[balajialg]

Thanks I'd like to give 🙌

• Thanks @yuvipanda for detailed instructions in Analyze the nbgitpuller log data to find the 3k discrepancy between course enrollment data and raw data from logs #2943 to retrieve the required logs from hub data!
• Thanks @felder for following up on the EECS performance-related issues consistently.

Updates from last week ✔

• Working on a presentation to introduce Datahub to RTL leadership tomorrow!
• Trying to analyze the historical log data downloaded from Google cloud-based on Yuvi's instructions. Making baby steps with regards to this analysis as of now.
• Updated Real-Time Collaboration write up in the curriculum guide jupyter book.
• Iterating on this version of the newsletter and plan to align folks at DSUS next week.
• Thanks to @yuvipanda's nudge, wrote the product and team principles document to align on some important decisions. Hopefully, will refer back to this document to make important decisions going forward.
• Scheduled a follow-up discussion with Ischool folks regarding the Hub point of contact (for Ischool) and also demo the admin functionality to aid effective troubleshooting.
• Curating the cards before the sprint planning and retro meeting on Thursday. Considering that last week was a holiday, have clubbed both the sprint planning and retro meeting together in 1 hour. Hopefully, it will be a productive session overall.

Challenges I faced and things I'd like assistance with 🙏

• Having a hard time moving our weekly update to a biweekly update through Github actions. Need help finding a cron metric that can make the GitHub actions run every alternate Monday,. (Ref: Schedule job to every 2 weeks node-schedule/node-schedule#455)

[balajialg]

@yuvipanda @felder FYI!

[felder]

@balajialg I do not believe posix cron syntax provides for a means of doing what you want.

Typically on a traditional cron implementation you'd either:

1. Incorporate a check (for example using the date command) with the && operator in the command for cron to execute: 0 7 8-14,22-28 * * [ `date +\%u\` = 1 ] && /path/to/myscript
2. Code in a check to the actual script cron runs.

In either case, cron will run more often than is necessary but perform a no-op until the secondary check succeeds.

Some other implementations support additional syntax that would let you specify this, but I do not believe github supports that.

In short, I don't think you can accomplish this in a scheduled github action.

[balajialg]

@felder Makes sense! Will manually close the issue every alternate week (going forward)