Skip to content

In GitHub Action, using version 3.40.0 of task to execute remote taskfile task reports vertex not found. #1931

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

Closed
iarchean opened this issue Nov 27, 2024 · 5 comments · Fixed by #2007
Labels
area: remote Changes related to remote taskfiles.

Comments

@iarchean
Copy link

  • Task version: 3.40.0
  • Operating system: GitHub Action ubuntu-latest
  • Experiments enabled: REMOTE_TASK_FILE

In GitHub Action, using version 3.40.0 of task to execute remote taskfile task reports vertex not found.

Here are the logs:

Run task --yes cloudrun:deploy SVC="@all" ENV="dev" CANARY="0"
The task you are attempting to run depends on the remote Taskfile at "https://storage.googleapis.com/xxx/cloudrun/Taskfile.yml".
--- Make sure you trust the source of this Taskfile before continuing ---
Continue? [assuming yes]
The task you are attempting to run depends on the remote Taskfile at "https://storage.googleapis.com/xxx/docker/Taskfile.yml".
--- Make sure you trust the source of this Taskfile before continuing ---
source vertex https://storage.googleapis.com/xxx/cloudrun/Taskfile.yml: vertex not found
Continue? [assuming yes]

However, when using version 3.37.1 of the task, there was no error, and it was successfully completed.
I haven't tried more versions yet, but I wanted to report this issue first.

@task-bot task-bot added the state: needs triage Waiting to be triaged by a maintainer. label Nov 27, 2024
@vmaerten
Copy link
Member

vmaerten commented Dec 7, 2024

Do you have a reproducible example ?
I am using remote taskfiles in github action at work and I have no issue. Therefore I am not able to reproduce.

@vmaerten vmaerten added state: awaiting response Waiting for issue author to respond. state: can't repro Not enough information was given to reproduce the issue described. and removed state: needs triage Waiting to be triaged by a maintainer. labels Dec 7, 2024
@vmaerten vmaerten closed this as not planned Won't fix, can't repro, duplicate, stale Feb 23, 2025
@ChrisPbb
Copy link

ChrisPbb commented Mar 3, 2025

Hello, fellow error-haver. I have also experienced this issue with remote Taskfiles but found it only happened when I did not specify the full path to the Taskfile. I think this is a sensible assumption to make but, to be fair, the documentation for remote taskfiles only shows support for URIs with a full path

This doesn't work

version: "3"

includes:
  foobar: https://example.com/taskfiles/foobar/

This works

version: "3"

includes:
  foobar: https://example.com/taskfiles/foobar/Taskfile.yaml

@jeongukjae
Copy link
Contributor

Hi, this is the fix that I submitted before and merged.
#2007

@pd93 pd93 linked a pull request Mar 4, 2025 that will close this issue
@pd93
Copy link
Member

pd93 commented Mar 4, 2025

That change has been merged, but not released yet. It will be in the next release, which will hopefully be in the coming days.

@pd93 pd93 closed this as completed Mar 4, 2025
@pd93 pd93 added area: remote Changes related to remote taskfiles. and removed state: awaiting response Waiting for issue author to respond. state: can't repro Not enough information was given to reproduce the issue described. labels Mar 4, 2025
@jeongukjae
Copy link
Contributor

@pd93 do you have brief eta for next release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: remote Changes related to remote taskfiles.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants