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

[Bug] Build the website source step fails as of #359 #360

Open
nsryan2 opened this issue Jan 30, 2025 · 2 comments
Open

[Bug] Build the website source step fails as of #359 #360

nsryan2 opened this issue Jan 30, 2025 · 2 comments

Comments

@nsryan2
Copy link
Member

nsryan2 commented Jan 30, 2025

Describe the bug.

PR #359 adds Bryan to the website with a photo and description. Both of which appear to be correct, yet the GitHub action to build the site fails at the Build the website source step.

Steps to reproduce the bug.

Steps to reproduce the behavior (ideally as a minimum example of where the failure is coming from with code blocks for error messages and inputs):

  1. Adding Bryan photo and description #359 adds a photo to img/people/ and replicates the personal block in the _data/people.yml.
  2. Upon merging, the error we've shared in Additional Context prevents the completion of the Build the website source step.

We think the error could come from an unspecified version in gem or one of the other dependencies pulling a new update that is incompatible with the existing gem file.

What inputs and outputs are involved?

The appropriate workflow can be found here: https://github.com/arfc/arfc.github.io/blob/source/.github/workflows/deploy-site.yml

Are there additional replication details?

What is the expected behavior?

We expect that the GitHub action should be successful in building the website as before as we have not changed the gem file or any explicit version information.

Additional context.

The full error at this step is as follows:

0s
Run bundle exec rake generate
  bundle exec rake generate
  shell: /usr/bin/bash -e {0}
bundler: failed to load command: rake (/home/runner/work/arfc.github.io/arfc.github.io/vendor/bundle/ruby/2.7.0/bin/rake)
/opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/runtime.rb:304:in `check_for_activated_spec!': You have already activated uri 0.10.0.2, but your Gemfile requires uri 1.0.2. Since uri is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports uri as a default gem. (Gem::LoadError)
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/runtime.rb:25:in `block in setup'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/spec_set.rb:165:in `each'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/spec_set.rb:165:in `each'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/runtime.rb:24:in `map'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/runtime.rb:24:in `setup'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler.rb:162:in `setup'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/setup.rb:23:in `block in <top (required)>'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/ui/shell.rb:159:in `with_level'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/ui/shell.rb:111:in `silence'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/setup.rb:23:in `<top (required)>'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/cli/exec.rb:56:in `require_relative'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/cli/exec.rb:56:in `kernel_load'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/cli/exec.rb:23:in `run'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/cli.rb:492:in `exec'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/vendor/thor/lib/thor/command.rb:28:in `run'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/vendor/thor/lib/thor.rb:527:in `dispatch'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/cli.rb:34:in `dispatch'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/vendor/thor/lib/thor/base.rb:584:in `start'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/cli.rb:28:in `start'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/exe/bundle:37:in `block in <top (required)>'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/lib/ruby/gems/2.7.0/gems/bundler-2.4.22/exe/bundle:29:in `<top (required)>'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/bin/bundle:23:in `load'
	from /opt/hostedtoolcache/Ruby/2.7.8/x64/bin/bundle:23:in `<main>'
Error: Process completed with exit code 1.
0s

How can this issue be closed?

This issue can be closed with a PR either fixing the input or updating the gem file to avoid this error.

@katyhuff
Copy link
Member

Did @yardasol set up this github action?

@katyhuff
Copy link
Member

I suspect this is caused by bundler-cache: true in the workflow.
On a terminal, this might be a moment for bundle clean -force
Since this is GitHub, I'm going to make a test pr that alters the yml doc for the deploy workflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment