We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I was testing another feature and discovered a data race had slipped into the child/ code in the last commit. It is a race between line...
consul-template/child/child.go
Line 277 in dc274bc
Line 376 in dc274bc
The cmd.Wait() in start() is run in a goroutine and it updates cmd.ProcessState internally. Which that c.cmd.ProcessState access in kill() races with.
cmd.Wait()
start()
cmd.ProcessState
c.cmd.ProcessState
kill()
Note that triggering this race in production would be hard, which is why I think no one ran into it (or at least reported it).
I'm working on a fix which I will be pushing up a PR for shortly, but wanted an issue for the record.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
I was testing another feature and discovered a data race had slipped into the child/ code in the last commit. It is a race between line...
consul-template/child/child.go
Line 277 in dc274bc
And line...
consul-template/child/child.go
Line 376 in dc274bc
The
cmd.Wait()
instart()
is run in a goroutine and it updatescmd.ProcessState
internally. Which thatc.cmd.ProcessState
access inkill()
races with.Note that triggering this race in production would be hard, which is why I think no one ran into it (or at least reported it).
I'm working on a fix which I will be pushing up a PR for shortly, but wanted an issue for the record.
The text was updated successfully, but these errors were encountered: