-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
JSON workers should delimit work requests with newlines #14218
Labels
Comments
I agree, see #13599 (comment) |
gregestren
added
team-Performance
Issues for Performance teams
untriaged
type: feature request
labels
Nov 18, 2021
@wolfd Do you want to make a PR against the 5.0 rc? Seems like a good thing to try to get in. |
wolfd
added a commit
to wolfd/bazel
that referenced
this issue
Nov 23, 2021
JSON persistent workers now delimit requests with newlines (`\n` on Unix, `\r\n` on Windows). Fixes bazelbuild#14218. Closes bazelbuild#14219. PiperOrigin-RevId: 411596359
meteorcloudy
pushed a commit
that referenced
this issue
Nov 24, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the problem / feature request:
JSON workers are difficult to write because work requests are not newline delimited. This issue was brought up in #13599, and the discussion generally indicated that this is a usability bug.
The proposal is to add a newline between requests according to ndjson.
Feature requests: what underlying problem are you trying to solve with this feature?
Right now an implementation of a JSON worker work request loop using python looks like this:
With newline-delimited JSON it would look like this:
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Current version
Proposed version
The text was updated successfully, but these errors were encountered: