Skip to content
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

Move over to the official bazel_worker implementation #68

Merged
merged 3 commits into from
Jan 21, 2025

Conversation

Bencodes
Copy link
Owner

@Bencodes Bencodes commented Jan 16, 2025

Migrating over to the official Bazel worker implementation so that these rules don't have to maintain their own internal implementation.

This PR also moves the underlying worker communication from json over to proto.

@Bencodes Bencodes force-pushed the move-over-to-the-official-bazel_worker-implementation branch from 84426cc to a2d58bf Compare January 17, 2025 18:20
@Bencodes Bencodes force-pushed the move-over-to-the-official-bazel_worker-implementation branch from a2d58bf to 49fd781 Compare January 17, 2025 18:33
},
realStdErr,
ProtoWorkerMessageProcessor(System.`in`, System.out),
).setCpuUsageBeforeGc(Duration.ofSeconds(10))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can I ask what the purpose of setting this is and why you chose 10 seconds specifically?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copied this from the usages within Bazel core and their examples.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good, the PR looks good to me from my perspective.

@Bencodes Bencodes merged commit ae06a63 into main Jan 21, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants