You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] - Issue Title cse 2.8.20版本 org.apache.servicecomb.foundation.vertx.stream.BufferInputStream流 int read()方法读取单字节,如果读取到流末尾会抛异常IndexOutOfBoundsException #4778
As already pointed to in the earlier comment, #5059 was merged into 2.9.x on 28 January 2026. The same int read() end-of-stream change was also merged into 2.8.x in #5063 on 30 January 2026: when no bytes remain, read() returns -1 instead of calling readUnsignedByte().
The first published releases that contain this change are 2.8.30 and 2.9.3. Later 2.8.x / 2.9.x releases such as 2.8.31 and 2.9.5 include it as well. 2.8.20, and the earlier published 2.8.29 / 2.9.2 tags, still have the unguarded read() path.
Could you retry your reproducer on a published 2.8.30+ or 2.9.3+ release and tell us whether the IndexOutOfBoundsException is gone?
Activity
liubao68 commentedon Apr 16, 2025
可以帮助提交一个PR修复这个问题吗?
chengyouling commentedon Jan 27, 2026
see: #5059
hezhangjian commentedon Nov 13, 2026
Thanks for the detailed reproducer.
As already pointed to in the earlier comment, #5059 was merged into
2.9.xon 28 January 2026. The sameint read()end-of-stream change was also merged into2.8.xin #5063 on 30 January 2026: when no bytes remain,read()returns-1instead of callingreadUnsignedByte().The first published releases that contain this change are 2.8.30 and 2.9.3. Later 2.8.x / 2.9.x releases such as 2.8.31 and 2.9.5 include it as well. 2.8.20, and the earlier published 2.8.29 / 2.9.2 tags, still have the unguarded
read()path.Could you retry your reproducer on a published 2.8.30+ or 2.9.3+ release and tell us whether the
IndexOutOfBoundsExceptionis gone?