Skip to content

Fix CI Build Timeout by Using Local Geist Fonts#24

Merged
VulcanoSoftware merged 1 commit into
mainfrom
fix-ci-font-fetch-timeout-3475021281854471409
Jul 5, 2026
Merged

Fix CI Build Timeout by Using Local Geist Fonts#24
VulcanoSoftware merged 1 commit into
mainfrom
fix-ci-font-fetch-timeout-3475021281854471409

Conversation

@VulcanoSoftware

Copy link
Copy Markdown
Owner

I have resolved the GitHub Action failure by switching the frontend font management from next/font/google to the standalone geist package.

The logs showed that the ARM64 Docker build was failing during npm run build because it timed out while attempting to fetch Geist Mono from Google Fonts. By installing the geist package and using it locally, we eliminate this network dependency during the build process.

I have verified the fix by:

  1. Running npm run build and npm run lint successfully in the dcfs-gh-pages directory.
  2. Visually verifying the frontend using a Playwright script that captured screenshots of the application running with the new font configuration.
  3. Ensuring no temporary files (like next_dev.log) are included in the submission.

PR created automatically by Jules for task 3475021281854471409 started by @VulcanoSoftware

Switched from `next/font/google` to the `geist` NPM package in the
`dcfs-gh-pages` frontend. This avoids external network requests to
Google Fonts during the build process, which was causing timeouts
in the ARM64 Docker build environment.

- Added `geist` to `dcfs-gh-pages/package.json`
- Updated `dcfs-gh-pages/app/layout.tsx` to use local fonts
- Verified build and lint pass locally

Co-authored-by: VulcanoSoftware <113239901+VulcanoSoftware@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@VulcanoSoftware VulcanoSoftware marked this pull request as ready for review July 5, 2026 11:53
@VulcanoSoftware VulcanoSoftware merged commit 7f72e1e into main Jul 5, 2026
1 check passed
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.

1 participant