github release deployment fails due to "uninitialized constant faraday::error::clienterror"
[affected build](https://travis-ci.org/3dstris/3dstris/builds/632815091)

everything seems to work until deployment. not sure if i’m doing anything wrong, but as previous builds (from nearly 20 days ago) worked, i doubt it.
duplicate of

[image]

[there was an error while trying to load the gem 'octokit'](https://travis-ci.community/t/there-was-an-error-while-trying-to-load-the-gem-octokit/6708) [linux](/c/environments/linux)

i don’t know what happend, and who can help me.

<https://travis-ci.com/jd-ftf/wot-design-mini/builds/142953099>
[[image]](https://aws1.discourse-cdn.com/business4/uploads/travis_ci/original/2x/6/6f9df34499e7f048c9ff9d0d369c1a4a450f4e1b.png "image")
hello [@cjiang1](/u/cjiang1),

welcome to gitlab forum - thanks for your first contribution :slightly\_smiling\_face:

i think this is most probably caused by a misconfiguration - here’s an [example](https://gitlab.com/gitlab-org/gitlab-ce/issues/48349#note_129188834), fyi. [image] cid\_cat:

error: c++11 is required and is missing or failed to compile.

i can’t help with most of that, but for c++11, see:

<https://gcc.gnu.org/projects/cxx-status.html#cxx11>

you probably must explicitly pass argument “-std=c++11” (or in some cases, perhaps “-std=gnu++11”).

if you l… > You might have missed a bracket somewhere... Only such a mistake causes so many insignificant errors.
> 
> 


And to find it, [format your code](http://www.gidnetwork.com/b-38.html) properly. It's your first debugging tool. [@andrey-olishchuk](/u/andrey-olishchuk) the issue is fixed i was able to deploy your project we believe this issue has been fixed with our most recent release, version 10.9.
 


 you can learn more here:
 



 please try updating, and let me know if you have any other questions.
 


  
 


 also, if you are experiencing this issue via the web client, please let us know here: since the error is on websockets, it is almost certainly a proxy layer somewhere that doesn’t support websockets, which is different on the two clusters (i.e. between you and any jupyterhub’s proxy-public entrypoint, rather than any part of jupyterhub itself or any of jupyterhub’s own configuration)… this is a known issue, we are currently working on it and it should be fixed in the 3.0 patch. pull request sent and accepted. this bug is resolved. hi [@petr\_kibukevich](/u/petr_kibukevich) 
issue has been fixed and deployed to cloud servers. please verify whether everything works fine now 
anton update: resolved.

my github actions workflow was configured for windows. this was no problem up until the sonarcloud task. i now configured it to run on linux and now the workflow succeeds across the board.

name: .net core

on: [push]

jobs:

build:

runs-on: ubuntu-latest