-
Notifications
You must be signed in to change notification settings - Fork 1
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
Connection refused in the CI #9
Comments
Ah, so you can add some private files in the repo, how do you do that? |
They are not files, but really tokens. From the Settings tab (ask @scarrazza) you can add some key-value pairs, and they are accessible during workflows. https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions
It's not your personal repo, so you should not use your personal token :) |
Thanks, could you please use the new secrets: |
Ok thanks, so are they some kind of shell variables that I can read with |
Yes, exactly. Load from secrets and assign with environment. |
Okay, I managed to make the tests run. Unfortunately I had to copy the Anyway, the |
Does it work outside tests? (I am using the test token that you have) |
No I am still getting the connection error:
By default it's using port 80 though, should I change it? |
No, at the moment we are using 8080. |
Solved in #11. |
Tests are failing.
https://github.com/qiboteam/qibo-cloud-backends/actions/runs/8084328381/job/22089366544
I just took a quick glance, and I believe you should add the tokens as secrets in the repo, such that you could access them from the workflow.
The text was updated successfully, but these errors were encountered: