Skip to content
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

GitHub action #115

Draft
wants to merge 11 commits into
base: main
Choose a base branch
from
Draft

GitHub action #115

wants to merge 11 commits into from

Conversation

dcjohnson24
Copy link
Collaborator

Description

Download data.json and schedule_vs_realtime_all_day_types_routes.json from s3. Commit the changes to GitHub.

Checklist

  • I am requesting to merge into the dev branch
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings

Screenshots

Before After

@netlify
Copy link

netlify bot commented Oct 25, 2023

Deploy Preview for sprightly-muffin-751ffc ready!

Name Link
🔨 Latest commit 820743b
🔍 Latest deploy log https://app.netlify.com/sites/sprightly-muffin-751ffc/deploys/659922a166116000088abddf
😎 Deploy Preview https://deploy-preview-115--sprightly-muffin-751ffc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@netlify
Copy link

netlify bot commented Oct 25, 2023

Deploy Preview for creative-quokka-61f1f5 ready!

Name Link
🔨 Latest commit 820743b
🔍 Latest deploy log https://app.netlify.com/sites/creative-quokka-61f1f5/deploys/659922a185ff190007e7bf9f
😎 Deploy Preview https://deploy-preview-115--creative-quokka-61f1f5.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@dcjohnson24 dcjohnson24 marked this pull request as draft October 25, 2023 00:28

jobs:
download-data-json:
runs-on: macos-latest
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May I know the context around the choice for running on macos instead of ubuntu?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

macos runners have 14 GB of RAM, but ubuntu only has 7. https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners. This was an issue for one of the backend jobs, but ubuntu might be fine for this one.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no concerns with macos. I was just concerned about whether we were running up against some memory limits that we might some day exceed again.

steps:
- uses: actions/checkout@v3
- run: |
wget https://chn-ghost-buses-public.s3.us-east-2.amazonaws.com/frontend_data_files/data.json \
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently the backend is uploading files to s3 at cta_schedule_zipfiles_raw/google_transit_{today}.zip. Is there a plan that the backend GitHub Action will be uploading updated json data at frontend_data_files/data.json and schedule_vs_realtime_all_day_types_routes.json? I see several backend PRs. Are there particular PRs I should focus on in the backend repo in order to understand what the files in s3 will consist of?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, data.json and schedule_vs_realtime_all_day_types_routes.json are created here. This is in PR #69.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the clarification. In this case, I'm ready to approve. Shall we convert to draft first so that we don't merge before chihacknight/chn-ghost-buses#69 is merged, or will we just remember the proper sequence of merging?

Copy link
Collaborator Author

@dcjohnson24 dcjohnson24 Nov 7, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, converting to a draft would be a good idea. I'll do that.

@dcjohnson24 dcjohnson24 marked this pull request as ready for review October 31, 2023 02:00
@dcjohnson24 dcjohnson24 changed the base branch from main to update-schedule-performance-data October 31, 2023 17:11
@dcjohnson24 dcjohnson24 changed the base branch from update-schedule-performance-data to main October 31, 2023 17:12
@dcjohnson24 dcjohnson24 marked this pull request as draft November 7, 2023 00:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants