-
-
Notifications
You must be signed in to change notification settings - Fork 760
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
ER: Fix dashboard data script (workflow) #6229
Comments
I would recommend checking if any of the secrets are expired first to see if this is the reason for the failures: https://github.com/hackforla/live-dashboard-automation/blob/444e9f010fe11e015acac6e9d2b14707398be049/.github/workflows/schedule_run_to_update_data.yaml#L56-L58 |
@ExperimentsInHonesty |
Hi Data Science people. I know someone from DS has been working on helping us get this dashboard script working again. Can you leave a note on this issue explaining what was done to fix it |
Hi @ExperimentsInHonesty, thank you for taking up this issue! Hfla appreciates you :) Do let fellow developers know about your:- You're awesome! P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :) |
|
Emergent Requirement - Problem
The workflow that updates the data on our issue dashboard is not working and has not worked for the last two weeks. I don't know exactly when because I can't find the date on the failed file, it just says 2 weeks.
Edit: It looks like the script is working now but we still need a GHA to notify us (by opening an issue).
Details
https://github.com/hackforla/live-dashboard-automation/actions/workflows/schedule_run_to_update_data.yaml
Issue you discovered this emergent requirement in
Date discovered
2024-01-28
Did you have to do something temporarily
Who was involved
@ExperimentsInHonesty
What happens if this is not addressed
Resources
Recommended Action Items
Potential solutions [draft]
In addition to getting the script working again, we need a GHA to notify us (by opening an issue) if it fails more than 2 times in a row and there is not an open issue already for it.
The text was updated successfully, but these errors were encountered: