-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Ensure that only the tokens needed are fetched #3722
Conversation
Signed-off-by: Tristan Swadell <tswadell@google.com>
Seems harmless enough and if it's mimicking C++ seems OK. Is the continuous integration system down @ericvergnaud ? |
There are some problems with self-hosted CI again on not Windows platforms. |
@ericvergnaud can you kick the CI? Seems like github actions, at least self hosted, are unreliable. I guess that means that if we bought some fancy server in the cloud it we have the same problem right? |
They are already fine at least here: #3725. Is it possible just to restart the build? |
Yes, I guess it's more reliable and preferable option. |
I restarted failed jobs. |
oh and now it says all fine. that was fast. maybe too fast. haha |
Update the Go and Java runtimes to match the C++ runtime for syncing to only the tokens needed
to read the text from the supplied interval.
The
fill()
methods search for EOF as a signal to conclude the token syncing; however, when thereis an errant input, EOF may be missing and this can result in
fill()
re-reading the entire token streamfor each error encountered in the input. As such
fill()
has been replaced withsync()
calls whichprovide equivalent functionality.
Signed-off-by: Tristan Swadell tswadell@google.com