You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Post-cleanup GPG action fails if the same key is imported twice. This generates unnecessary warning that is not possible to correct from the user's perspective.
Some background: I have an action which downloads latest translations of my project from third-party service. Due to the way how it works, and the fact that it's currently impossible to set git config properties globally (see #92), I actually use your action to commit and push in two different repos in one action: a subdirectory wiki repo (which is a git submodule), and the main repo.
GPG action should not generate a warning that comes from the result of trying to remove the same key twice. One of the solutions might be to check if the key is in fact in the keystore prior to trying to remove it.
I'm unsure whether it won't be needed to deal with double agent-killing as well in this regard.
Actual behaviour
Second post-cleanup job generates this warning:
Post job cleanup.
🚿 Removing keys
Warning: gpg: key "<somekey>" not found: Not found
gpg: <somekey>: delete key failed: Not found
This isn't critical bug because only warning is generated and the workflow otherwise works properly, but it's definitely something that should be corrected in regards to planned use cases.
Side note: with enhancement mentioned in #92, the "proper" workaround for this issue might be "just import your key once globally instead". It'd definitely work for my case, but if somebody would indeed want to go full local with the same key in two different repos, he'll still get this warning.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
@JustArchi I hadn't thought of using this action several times in the same job and indeed it causes an issue in post step. #92 should mitigate this issue like you said but we could enhance the post step and check if the key actually exists and/or the agent is running.
Behaviour
Post-cleanup GPG action fails if the same key is imported twice. This generates unnecessary warning that is not possible to correct from the user's perspective.
Some background: I have an action which downloads latest translations of my project from third-party service. Due to the way how it works, and the fact that it's currently impossible to set git config properties globally (see #92), I actually use your action to commit and push in two different repos in one action: a subdirectory
wiki
repo (which is a git submodule), and the main repo.See https://github.com/JustArchiNET/ArchiSteamFarm/runs/2646297703 as an example.
Steps to reproduce this issue
Import the same key twice in two different actions.
Expected behaviour
GPG action should not generate a warning that comes from the result of trying to remove the same key twice. One of the solutions might be to check if the key is in fact in the keystore prior to trying to remove it.
I'm unsure whether it won't be needed to deal with double agent-killing as well in this regard.
Actual behaviour
Second post-cleanup job generates this warning:
Configuration
Logs
logs_4363.zip
Additional information
This isn't critical bug because only warning is generated and the workflow otherwise works properly, but it's definitely something that should be corrected in regards to planned use cases.
Side note: with enhancement mentioned in #92, the "proper" workaround for this issue might be "just import your key once globally instead". It'd definitely work for my case, but if somebody would indeed want to go full local with the same key in two different repos, he'll still get this warning.
Thanks in advance.
The text was updated successfully, but these errors were encountered: