-
-
Notifications
You must be signed in to change notification settings - Fork 625
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
Cannot include multiple time the same Taskfile with differents namespaces #1606
Comments
@vmaerten @davinkevin It is definitely possible! Please could you give the changes in #1607 a go. Thanks |
Hi ! I've been running Task's output
I have 3 kind of errors :
The taskfile is the following : https://github.com/vmaerten/taskfile-demo/blob/main/Taskfile.yml Let me know if you need more precision or if I can help :) |
Can you confirm that you're running on b0e58c6? I've checked out your project and am unable to reproduce. |
But I can also provide a Github action that fail with this error, however it seems harder to trigger it in GH action (https://github.com/vmaerten/taskfile-demo/actions/runs/8774178400/job/24075110053 or https://github.com/vmaerten/taskfile-demo/actions/runs/8774252202/job/24075264726) |
@vmaerten Thanks, as you said, it looks like a simple race condition between the go routines. I've added a mutex and pushed a commit. Please let me know if this works for you. |
No problem! Thanks for being proactive and spotting this before it got released. As for the output, I have noticed this before, but never found the root cause. It can happen in other situations too. I have some plans to look into our formatter at some point. I'll definitely keep this in mind when I get to it. |
Hi,
Following this comment, I've opened an issue to track this.
I am using this pattern a lot, in almost in every project (around 20). The idea is to have on Taskfile per language and standardise all Tasks for all projects.
Here the repo to reproduce : https://github.com/vmaerten/taskfile-demo
You can run
go run ./cmd/task --dir ./taskfile-demo deploy/dev -f
I have this error :
I've given a talk at devoxxfr last thurday presenting Task (using this repo), and when discussing with attendees, multiple people have the same use case.
I think @davinkevin has the same use case.
The next release will most likely break some setup. Is it possible to get DAG working with this setup ?
The text was updated successfully, but these errors were encountered: