Gradle Encountered end-of-stream mid-frame

[milic-marko]

Extension Name: vscode-gradle
Extension Version: 3.17.3
OS Version:
VSCode version: 1.116.0

Describe the bug
Gradle wont run tasks

WARNING: Exception processing message
io.grpc.StatusRuntimeException: INTERNAL: Encountered end-of-stream mid-frame
	at io.grpc.Status.asRuntimeException(Status.java:530)
	at io.grpc.internal.AbstractServerStream$TransportState.deframerClosed(AbstractServerStream.java:234)
	at io.grpc.netty.NettyServerStream$TransportState.deframerClosed(NettyServerStream.java:164)
	at io.grpc.internal.MessageDeframer.close(MessageDeframer.java:234)
	at io.grpc.internal.MessageDeframer.deliver(MessageDeframer.java:301)
	at io.grpc.internal.MessageDeframer.request(MessageDeframer.java:162)
	at io.grpc.internal.AbstractStream$TransportState$1RequestRunnable.run(AbstractStream.java:236)
	at io.grpc.netty.NettyServerStream$TransportState$1.run(NettyServerStream.java:198)
	at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:566)
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:998)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:1474)
[error] Error running build: assemble: Call cancelled

Output from "Gradle for Java"
You can find this by clicking on the "Output" panel, then selecting the "Gradle for Java" channel from the dropdown.

Does the bug still exist if you disable all other extensions?
Yes/No

Additional context
Add any other context about the problem here.

[github-actions]

Hi @mamilic, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

• Update VS Code and the Gradle extension to the latest available versions.
• Enable debug logging for the language server by adding the following to your settings.json:

  "gradle.languageServerLogLevel": "DEBUG"

  Then, open the Output panel and select Gradle for Java to capture the full gRPC handshake and any errors.
• From a terminal, stop all Gradle daemons and run the same task manually to isolate the extension:

  gradle --stop
  ./gradlew assemble --stacktrace

• Disable all other extensions and reload the window to rule out conflicts. Report whether the error still occurs.
• Share the complete Gradle for Java output logs and confirm your VS Code version, OS, JDK version, and whether you’re using a Gradle wrapper or system Gradle.

No existing issue in the vscode-gradle repo explicitly mentions an end-of-stream mid-frame gRPC error.

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

[chagong]

Looks like the connection between vscode-gradle extension and Gradle Task server is broken. @mamilic, can you check if the Gradle daemon is alive or not on your machine? You can look for it on Gradle tree view explorer.

[milic-marko]

Hi @chagong , I haven't seen this error since. But will keeo an eye. Thanks!

[misterdlt]

Our team has been getting this issue on and off.

It seems like the recent 13.7.3 update of the Gradle for Java VS Code Extension introduced this bug.

We had to downgrade the extension to version 13.7.2 from 3 months ago to resolve the issue.

[wenytang-ms]

Thanks for the additional reports.

The Call cancelled message suggests that the Gradle task execution request was cancelled or the connection between the
extension and the Gradle task server was interrupted. We are still investigating the root cause.

For anyone who can still reproduce this, could you please help verify the following?

1. Try setting:

"gradle.reuseTerminals": "off"

Then reload VS Code and run the same Gradle task several times. Please let us know whether the intermittent failure still
happens.

1. Please share the full Gradle for Java output logs around a failed run. If possible, enable debug logging first:

"gradle.debug": true

Then reload VS Code, reproduce the issue, and attach the updated logs.

1. Please also confirm:

• VS Code version
• Gradle for Java extension version
• OS
• JDK version
• Gradle / Gradle wrapper version
• Whether the same task succeeds consistently when run directly from a terminal, for example ./gradlew assemble

This will help us determine whether the failure is caused by the Gradle task server connection itself or by task terminal reuse
in VS Code.