- Notifications
You must be signed in to change notification settings - Fork928
fix(agent): start rpty lifecycle after all reads/writes#15535
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
mafredri left a comment• edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
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.
Oh I was actually wondering about this but didn't check deeper since the race test didn't catch it.How did you catch it? (Oops, should've read the description.)
That other race test didn't win the race! 😆 |
12a9d63
intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Fixescoder/internal#214
#15475 missed that we also write to
rpty
after startingrpty.lifecycle()
.This PR moves the function call right at the end. Hopefully this should address the data races before we go resorting to mutexes.