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

Support cache-dependency-paths outside the current directory #361

Open
PeterJCLaw opened this issue Mar 27, 2022 · 10 comments
Open

Support cache-dependency-paths outside the current directory #361

PeterJCLaw opened this issue Mar 27, 2022 · 10 comments
Assignees
Labels
bug Something isn't working

Comments

@PeterJCLaw
Copy link

Description:

I'm building a composite Action which uses actions/setup-python internally. When specifying the requirements.txt from the action setting up Python fails, though I thiiink I'm passing the right values.

Here's what I've got:

    - name: Set up Python
      uses: actions/setup-python@v3
      with:
        python-version: '3.10'
        cache: pip
        cache-dependency-path: ${{ github.action_path }}/requirements.txt

Here's the error I get:

No file in /home/runner/work/sr2022-comp/sr2022-comp matched to [/home/runner/work/_actions/PeterJCLaw/srcomp-validate-action/bd809ff12b77607cc2f0ebbd035d6f0a5c8d32fc/requirements.txt], make sure you have checked out the target repository

sr2022-comp is the repo I'm using to test the action, srcomp-validate-action is the action.

My specific use-case only has a couple of dependencies so #351 would likely work as a fix, though I can imagine that a more complex scenario would want this to work.

Platform: Ubuntu

@PeterJCLaw PeterJCLaw added bug Something isn't working needs triage labels Mar 27, 2022
@PeterJCLaw
Copy link
Author

I'm currently working around this by coping the requirements file into a temporary directory within the working directory and then referencing that, instead of the original. This doesn't feel like a great solution though as it ends up polluting the target repo's working copy.

@dmitry-shibanov
Copy link
Contributor

Hello @PeterJCLaw. Thank you for your report. Could you please provide a public repository to reproduce the issue ?

@dmitry-shibanov
Copy link
Contributor

Hello @PeterJCLaw. Actually, I think the root cause of the issue in the toolkit/glob package. The hashFiles function tries to compare if the passed directory matches with GITHUB_WORKSPACE. The composite action's directory and checkout project's directory don't match, that is why if does hash the file and the actions setup-python throws an error.

@PeterJCLaw
Copy link
Author

Thanks for your replies.
For completeness the repos in question are:

I've raised actions/toolkit#1035 for the underlying issue.

@dmitry-shibanov dmitry-shibanov self-assigned this Mar 31, 2022
@dmitry-shibanov
Copy link
Contributor

Hello @PeterJCLaw. For now I'm going to close the pull request because the root cause of the issue comes from the toolkit repository. If you have any concerns feel free to ping us.

karlicoss added a commit to karlicoss/HPI that referenced this issue Apr 15, 2022
@PeterJCLaw
Copy link
Author

@dmitry-shibanov would you be open to reopening this issue? It looks like hashFiles has a new parameter now which allows callers to specify the workspace directory (actions/toolkit#1318), which I think would help here?

@dmitry-shibanov
Copy link
Contributor

dmitry-shibanov commented Aug 17, 2023

Hello @PeterJCLaw. In this case I'm coming to reopen the issue to investigate it one more time.

edit: Sorry for edit in the first glance I thought it was a pull request.

@zyv
Copy link

zyv commented Oct 25, 2023

@dmitry-shibanov we also got hit by this one, any news whether this can be addressed now, that there is a new parameter in toolkit available?

@jaimehrubiks
Copy link

I'm also hit by this issue, I guess this line is quite common:

${{ github.action_path }}

@zyv
Copy link

zyv commented Apr 28, 2024

@dmitry-shibanov any progress on that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants