Closed Silverlan closed 9 months ago
thanks for the issue report. i was able to replicate the issue locally and suspect a small bug in parsing of the branch/tag/commit information from the config JSON.
not sure why it would only break now -- except, a new official Vulkan SDK did come out this week, so it's possible the web services / configuration files were updated. continue to investigate
I dont know why or how but it is working again in my repo without changing anything related to GitHub Actions.
I dont know why or how but it is working again in my repo without changing anything related to GitHub Actions.
Can confirm, it's working for me again as well. I'll leave the issue open for now since the cause is still unknown.
Thanks for the follow-ups (it is also started working for me suddenly).
Root cause apparently interim changes on LunarG's side, but checking their bug tracker, I don't see any recent issues filed/closed about it (https://vulkan.lunarg.com/issue/home).
In any event, the ambiguous error message bothers me and I am planning to add a few more webservice/config preflight checks into the upcoming v1.2.1 release. cc: #12
having been unable to repro again, closing this given #12 merges better error reporting that theoretically will help catch these kinds of nuances moving forward. thanks!
This action has been working fine for me until yesterday, but now I can't get it to succeed anymore. It fails with the following error:
2022-10-26T07:23:34.7120775Z parse error: Invalid numeric literal at line 1, column 7
Here is the entire log:
My test workflow is very basic and just looks like this:
https://github.com/Silverlan/test_github_action_vulkan/blob/main/.github/workflows/pragma-linux-ci.yml