-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
DV2 TypingDedupingTest: read container stdout in real time #34173
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
); | ||
messageHandler.submit(() -> { | ||
while (!destination.isFinished()) { | ||
destination.attemptRead(); |
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.
I didn't see another call for attemptRead so seems safe but just a note that attemptRead isn't thread safe.
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.
yep it's only called from here. I'll add a comment though
no need to publish cdk since T+D isn't (yet) in the cdk. No need to publish connectors since this is just test code. merging directly. |
discovered accidentally - if a connector container logs too much to stdout, it eventually gets blocked because the buffer fills up. Dump stdout in a background thread instead.
I could be convinced to pass the executor service / future through to the
endSync
method? but that seemed overkill