-
-
Notifications
You must be signed in to change notification settings - Fork 770
feat: improve fingerprint, run and output with wildcard #1808
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
Conversation
feb5d44 to
dab7cb3
Compare
task.go
Outdated
| call.Vars = &ast.Vars{} | ||
| } | ||
| call.Vars.Set("MATCH", ast.Var{Value: matchingTasks[0].Wildcards}) | ||
| matchingTasks[0].Task.FullName = call.Task |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like we'd be getting a race condition here, no? Parallel calls to this task would be overiding the same attribute.
Tricky to implement this in another way, though, I know...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are totally right. The same task with a wildcard, used twice in a dep (ran in parallel) the first one will be overridden by the last
Put this in draft until I find a solution for it
Thanks!
4cd0f48 to
15d6799
Compare
|
Finally took the time to finish this! |
andreynering
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's working perfectly. Thank you!
Do not forget to mention this on CHANGELOG after merging.
Fixes :
It also improve the output, now the task with wildcard replaced are displayed :
I was struggled a bit with the naming. I choose
Fullnamebut feel free if you have a better idea.