Skip to content

Use custom version of java_stub_template to avoid orphaned processes #88

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

Merged
merged 1 commit into from
Mar 25, 2025

Conversation

jjudd
Copy link

@jjudd jjudd commented Mar 24, 2025

This updates the rule set to use a custom version of the java_stub_template in order to avoid an issue with orphaned processes due to long classpaths.

See this Bazel issue for more info:
bazelbuild/bazel#19036

This updates the rule set to use a custom version of the
java_stub_template in order to avoid an issue with orphaned processes
due to long classpaths.

See this Bazel issue for more info:
bazelbuild/bazel#19036
@jjudd jjudd requested review from JaredNeil and jadenPete March 24, 2025 23:53
@jadenPete
Copy link

To be clear, does this custom launcher script adopt @JaredNeil's first strategy?

Don't bother deleting it. It's in /tmp/ and probably a relatively small file (~10KB range).

@JaredNeil
Copy link
Member

To be clear, does this custom launcher script adopt @JaredNeil's first strategy?

Don't bother deleting it. It's in /tmp/ and probably a relatively small file (~10KB range).

No, this skips creating the classpath jar entirely and uses an argfile instead (bazelbuild/bazel#6354).

@jjudd jjudd merged commit 009f97d into lucid-master Mar 25, 2025
1 check 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.

3 participants