-
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
Remove the custom implementation of buffered input stream reader #36673
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
.../java/airbyte-cdk/core/src/main/kotlin/io/airbyte/cdk/integrations/base/IntegrationRunner.kt
Outdated
Show resolved
Hide resolved
.../java/airbyte-cdk/core/src/main/kotlin/io/airbyte/cdk/integrations/base/IntegrationRunner.kt
Show resolved
Hide resolved
3e6985a
to
cbd5205
Compare
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.
Yay! Using the same reader the platform uses, e.g. the built-in java one, seems like a good way to not be dropping data
baos.write(b.toInt()) | ||
lastWasNewLine = false | ||
emptyLines++ | ||
// We've occasionally seen this loop not exit |
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.
we're not adding any loop, so I don't think we're making the problem worse. And once every 1k lines should not be a problem. If it is, it's a problem on the side that's generating those empty lines IMO
cbd5205
to
624ccae
Compare
This removes our custom message reader and uses a standard one. It also will log every 1000 empty lines until a max of 10000 is reached and report the number of empty lines at the end.