-
Notifications
You must be signed in to change notification settings - Fork 206
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
Alpine image not auto-detected on Action #1262
Comments
@mvorisek yeah I noticed this. I'm not sure why there's a difference between running I will continue to look into this so that the warning is properly removed. |
Here https://github.com/atk4/core/blob/63a2d72bbf/.github/workflows/test-unit.yml#L135 is a repro if it helps. Also notice, we use custom Alpine container image https://github.com/atk4/core/blob/63a2d72bbf/.github/workflows/test-unit.yml#L14. Based on the likes it seems many people are affected. The solution should be probably https://superuser.com/questions/1435147/how-to-suppress-warning-this-key-is-not-certified-with-a-trusted-signature#1435150, ie. |
@thomasrockhu-codecov is there any progress on this issue? |
@mvorisek I've been digging into this for a bit now. I don't think that adding The warning message implies that the key has not been signed by the user
This means that you, the user, have not indicated you trust the key. As a result, unless you actually import the key and sign it yourself, we will not be able to do anything about the warning. As it is, the warning is just that, a warning, as the key is hard coded into the codebase. |
@thomasrockhu-codecov please kindly reopen this issue, we use |
@mvorisek oh! sorry I didn't realize that would happen. Let me dig in a little more then. |
@mvorisek I don't think this is related to trusted signature as the system gets past verification. What is curious are the log lines after |
👍 here is a minimal repro using GH Actions:
with local Docker and Does Codecov bundle some lib linked againts |
Alpine doesn't use glibc, it uses musl, which is not the same. Could be that. |
Yes. My concern is what package causes that issue, |
action@v4 uses https://github.com/codecov/codecov-cli. Specifically, Lines 54 to 56 in 8be6ba5
I think we use pyinstaller. |
Works now on c16abc2 - use: codecov/codecov-action@c16abc29c95fcf9174b58eb7e1abf4c866893bc8 # 4.1.1
# ... |
ours fails after upgrading to 4.2.0 https://github.com/superfluid-finance/protocol-monorepo/actions/runs/8606474561/job/23586919598 (we were upgrading it to fix the previous failure.) Frustratingly, we can't find a config now that works. |
We had to stick to Someone from Codecov should look into it as it affects a lot of users based on the votes count and the fact Alpine is very popular. The repro should be easy, use this plugin on Github workflow using |
@mvorisek I have made an underlying change to the action and in setting |
Unfortunately, there is still some issue: https://github.com/atk4/core/actions/runs/9093675020/job/24993133255?pr=411#step:11:30. |
@mvorisek ahhh, this is a different issue. what OS is your runner using? You may need to specify a different OS for the action
|
I am running on Alpine. If there needs to be some different binary uploaded, I belive the detection should be done on runtime by the GH action itself. |
@mvorisek you are correct, I have that on my list of things to do, but for now I just wanted you unblocked |
|
CI log:
v3 with the same config is passing without any issue, but we want to upgrade as Node 16 is deprecated.
The text was updated successfully, but these errors were encountered: