Gh_pages fails to deploy due to name error `uninitialized constant Faraday::Error::ClientError`

Example affected build

I committed a change to a repository that I maintain, the build ran and succeed generating the sources to the docs, but deployment fails when installing the ruby gem dependencies for the github pages provider. Could someone at Travis please look into this failure?

1 Like

I have the exact same error when deploying to github page using a react application in my case

https://travis-ci.com/clubcapra/capra_web_ui/builds/129484806

1 Like

i am seeing the issue when trying to create a release from my deploy steps.

travis.yml:

build:
https://travis-ci.com/razee-io/RemoteResourceS3/builds/129482448#L822

1 Like

It’s an error from Octokit. See

and

If Octokit does not release a new version in a couple of hours, we’ll publish a dpl gem that will pin faraday to < 0.16.0.

https://www.travis-ci.org/gzlock/danplayer/jobs/590539620

/home/travis/.rvm/gems/ruby-2.4.5/gems/octokit-4.6.2/lib/octokit/middleware/follow_redirects.rb:14:in `module:Middleware’: uninitialized constant Faraday::Error::ClientError (NameError)

622Did you mean? Faraday::ClientError

Hello, everyone.

I’ve released dpl-releases 1.10.13 and dpl-pages 1.10.13 to address this problem.

Please rerun the affected builds and report the results.

Thanks.

1 Like

The build now runs! Thanks @BanzaiMan !

1 Like

Same for me, that fixed the issue. Thank you!

Imprint