Skip to content

Conversation

@ejona86
Copy link
Member

@ejona86 ejona86 commented Nov 13, 2025

… back to the client 2 (#12477)"

This reverts commit 14087f8.

It caused the same failures as the previous attempt that was reverted in 7eab160. cl/831837315

java.lang.AssertionError: Failed executing read operation
	at io.grpc.internal.CompositeReadableBuffer.execute(CompositeReadableBuffer.java:328)
	at io.grpc.internal.CompositeReadableBuffer.executeNoThrow(CompositeReadableBuffer.java:336)
	at io.grpc.internal.CompositeReadableBuffer.readBytes(CompositeReadableBuffer.java:151)
	at io.grpc.internal.ReadableBuffers$BufferInputStream.read(ReadableBuffers.java:377)
	at io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller.parse(ProtoLiteUtils.java:205)
	at io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller.parse(ProtoLiteUtils.java:133)
	at io.grpc.MethodDescriptor.parseRequest(MethodDescriptor.java:307)

CC @panchenko

… back to the client 2 (grpc#12477)"

This reverts commit 14087f8.

It caused the same failures as the previous attempt that was reverted in
7eab160. cl/831837315

```
java.lang.AssertionError: Failed executing read operation
	at io.grpc.internal.CompositeReadableBuffer.execute(CompositeReadableBuffer.java:328)
	at io.grpc.internal.CompositeReadableBuffer.executeNoThrow(CompositeReadableBuffer.java:336)
	at io.grpc.internal.CompositeReadableBuffer.readBytes(CompositeReadableBuffer.java:151)
	at io.grpc.internal.ReadableBuffers$BufferInputStream.read(ReadableBuffers.java:377)
	at io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller.parse(ProtoLiteUtils.java:205)
	at io.grpc.protobuf.lite.ProtoLiteUtils$MessageMarshaller.parse(ProtoLiteUtils.java:133)
	at io.grpc.MethodDescriptor.parseRequest(MethodDescriptor.java:307)
```
@ejona86 ejona86 merged commit 322e488 into grpc:master Nov 13, 2025
15 of 17 checks passed
@ejona86 ejona86 deleted the revert-12477 branch November 13, 2025 23:34
@panchenko
Copy link
Contributor

Is there any more details how that happens? It would be great to have such a test here.

@ejona86
Copy link
Member Author

ejona86 commented Nov 14, 2025

No; only that stack trace. It'll take some investigation with the reproduction we have internally. It isn't a fast reproduction, but at least we have one.

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