Skip to content
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

Error: The configuration file "/home/runner/work/_temp/user-config-from-action.yml" is outside of the workspace #2145

Closed
p5 opened this issue Feb 15, 2024 · 6 comments

Comments

@p5
Copy link

p5 commented Feb 15, 2024

As of an hour ago, we have been receiving errors from the github/codeql-action/init@v3 action with no changes being made on our end.

This is happening during the "Load language configuration" step. Please see the below error:

  Error: The configuration file "/home/runner/work/_temp/user-config-from-action.yml" is outside of the workspace

Since there were no changes on our end, I feel a bug or backwards-incompatible change may have been introduced in a recent commit. I am looking to see if there's anything obvious I can find.

Edit:
A fix has been proposed 🎉
#2147

@p5
Copy link
Author

p5 commented Feb 15, 2024

The individual commit appears to be 191f59f which introduced the error

@p5
Copy link
Author

p5 commented Feb 15, 2024

I believe we have identified the commit which introduced the error, and the logic which is causing it.

This code requires the configuration file to be inside the workspace directory before proceeding
https://github.com/github/codeql-action/blob/main/src/config-utils.ts#L886-L902

But this doesn't account for 191f59f moving the configuration file outside the workspace, into a _temp directory

@angelapwen
Copy link
Contributor

angelapwen commented Feb 15, 2024

Thank you for the notification: we've identified the error and have a fix up at #2147 As soon as it's in main, we'll release again to v2 and v3.

@angelapwen
Copy link
Contributor

angelapwen commented Feb 15, 2024

The fix is merged, and we're going through the release process for v2 and v3 again. In the meantime, we've manually retagged v2 and v3 to the version prior to the faulty release, so workflows using those tags should already no longer be seeing this issue.

@p5
Copy link
Author

p5 commented Feb 15, 2024

Have confirmed our CodeQL workflows using @v3 are working again.
Thank you!

Will close this issue as complete.

@p5 p5 closed this as completed Feb 15, 2024
@angelapwen
Copy link
Contributor

Thank you also for identifying the commit with the error 😄 we were doing it at the same time internally and you were just as fast!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants