-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Wrong cache-key used for caching #80
Comments
tytan652
added a commit
to tytan652/obs-studio
that referenced
this issue
Apr 30, 2022
flatpak/flatpak-github-actions#80 This issue is preventing the removal of the cache-key in the actions inputs.
tytan652
added a commit
to tytan652/obs-studio
that referenced
this issue
Apr 30, 2022
flatpak/flatpak-github-actions#80 This issue is preventing the removal of the cache-key in the actions inputs to use the default cache key.
RytoEX
pushed a commit
to obsproject/obs-studio
that referenced
this issue
May 3, 2022
flatpak/flatpak-github-actions#80 This issue is preventing the removal of the cache-key in the actions inputs to use the default cache key.
davidmyersdev
pushed a commit
to davidmyersdev/obs-studio
that referenced
this issue
May 15, 2022
flatpak/flatpak-github-actions#80 This issue is preventing the removal of the cache-key in the actions inputs to use the default cache key.
I believe this one was fixed in #48, it just hasn't had a release since that was merged. I've been using |
Closing as already fixed, I will try to do a new release in the upcoming weeks |
DioEgizio
added a commit
to DioEgizio/PrismLauncher
that referenced
this issue
Nov 19, 2022
currently there's a [bug](flatpak/flatpak-github-actions#80) on the stable version of the flatpak action which causes the cache key to be wrong. this commit work arounds it Signed-off-by: DioEgizio <83089242+DioEgizio@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While trying to switch to default cache-key in obsproject/obs-studio#5137.
We were trying remove the
cache-key
settings when this issue happen.An unexpected issue has occurred:
https://github.com/bilelmoussaoui/flatpak-github-actions/blob/9b33ba80aec2fc2652e05f15f19929fa98182889/flatpak-builder/index.js#L209-L212
It seems that
cacheKey
even if empty does not fullfill the condition and generate a wrong cache key which ends up being-x86_64
in our situation.The text was updated successfully, but these errors were encountered: