Open ojecborec opened 2 months ago
/bounty $100
/attempt #655
with your implementation plan/claim #655
in the PR body to claim the bountyThank you for contributing to permitio/opal!
Add a bounty • Share on socials
Attempt | Started (GMT+0) | Solution |
---|---|---|
🟢 @ojecborec | Sep 18, 2024, 10:57:17 AM | #662 |
💡 @ojecborec submitted a pull request that claims the bounty. You can visit your bounty board to reward.
/attempt #655 https://github.com/permitio/opal/pull/662
@ojecborec @gemanor any progress on this issue?
@Abiji-2020 Still waiting for @obsd to help us with failing tests on #662
@Abiji-2020 Still waiting for @obsd to help us with failing tests on #662
okay, incase if you need another hand, i am ready for it .
The log file reads
- Create .env file
- Clone tests policy repo to create test's branch
Cloning into 'opal-tests-policy-repo'...
Load key "/home/runner/work/opal/opal/app-tests/opal-tests-policy-repo-key": error in libcrypto
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.
I've only added wget
package to apt-get install
statement. This fail seems to be unrelated to my change. Do you have any idea what is going on?
The log file reads
- Create .env file - Clone tests policy repo to create test's branch Cloning into 'opal-tests-policy-repo'... Load key "/home/runner/work/opal/opal/app-tests/opal-tests-policy-repo-key": error in libcrypto git@github.com: Permission denied (publickey). fatal: Could not read from remote repository.
I've only added
wget
package toapt-get install
statement. This fail seems to be unrelated to my change. Do you have any idea what is going on?
I had checked several PR's in the repo and all of them has this issue, it is not a problem with the code, it is a problem with the docker workflow:
https://github.com/permitio/opal/blob/master/.github/workflows/tests.yml#117 the error is that issue with the SSH key used to clone the repository, which is likely caused by a missing or misconfigured SSH key.
Thank you for the explanation. Is there anything I can help with?
Thank you for the explanation. Is there anything I can help with?
we can ask the maintainers to check on the secrets the correct values are given in the repository. As all the PR currently opened are facing this issue in the docker test.
Hey, we have an issue with the CI at the moment, some expired token of some sort. I'm waiting for someone else's help, hopefully I will be able to resolve it soon and get this merged 🌟
It is pending 1 reviewer at the moment.
When running the latest
permitio/opal-client:0.7.12
image as docker compose with followingcommand
the
./start.sh
script is never executed. The reason is thatwget
binary does not exists thereforreturns 127 exit code.