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
Have you checked that your issue isn't already filed?
I read through FAQ and searched through the past issues, none of which addressed my issue.
Yes, I have checked that this issue isn't already filed.
Bug description
The repo and website cannot be updated after my push.
How to reproduce the bug
In my last commit and push, I just updated the content in papers.bib and venues.yml. But i received a message that the deployment fails, which I have never seen before.
Error messages and logs
The error message you got, with the full traceback if available. Please paste it between these triple backticks.
The message is:
Cache not found for keys: setup-ruby-bundler-cache-v6-ubuntu-24.04-x64-ruby-3.2.2-wd-/home/runner/work/hanyangclarence.github.io/hanyangclarence.github.io-with--without--only--Gemfile.lock-913dc1a8978cee140e0d813c85ae6e145f785bbcd254b85b865e4451c39352fd, setup-ruby-bundler-cache-v6-ubuntu-24.04-x64-ruby-3.2.2-wd-/home/runner/work/hanyangclarence.github.io/hanyangclarence.github.io-with--without--only--Gemfile.lock-
And the screen shot of the error message website is:
What operating system are you using?
Windows
Where are you seeing the problem on?
Deployed site
More info
No response
The text was updated successfully, but these errors were encountered:
Have you checked that your issue isn't already filed?
Bug description
The repo and website cannot be updated after my push.
How to reproduce the bug
In my last commit and push, I just updated the content in papers.bib and venues.yml. But i received a message that the deployment fails, which I have never seen before.
Error messages and logs
The message is:
And the screen shot of the error message website is:
What operating system are you using?
Windows
Where are you seeing the problem on?
Deployed site
More info
No response
The text was updated successfully, but these errors were encountered: