Issue #22342 has been updated by nagachika (Tomoyuki Chikanaga). Backport changed from 3.3: UNKNOWN, 3.4: REQUIRED, 4.0: REQUIRED to 3.3: UNKNOWN, 3.4: DONE, 4.0: REQUIRED ruby_3_4 commit:0a33ab92c08c8d1dbba0b3c97781d16b40ac53a8 merged revision(s) commit:227006291d35b2255b3f7a888d75102c129b0472. ---------------------------------------- Bug #22342: IO#gets can ignore the limit argument in some edge cases https://bugs.ruby-lang.org/issues/22342#change-119228 * Author: rhenium (Kazuki Yamaguchi) * Status: Closed * Backport: 3.3: UNKNOWN, 3.4: DONE, 4.0: REQUIRED ---------------------------------------- `io.gets(rs, limit)` ignores the `limit` value and reads until `rs` is found or EOF, if the `limit`-th byte of the stream matches `rs`'s last byte and: 1. The potential start of the record separator, the `limit-rs.bytesize`-th byte of the stream is not at a character boundary ```ruby str = "\x83\\xxx".force_encoding("Windows-31J") # "ソxxx".encode("Windows-31J") IO.pipe("Windows-31J"){|r,w|w.write(str); w.close_write; p r.gets("\\", 2); p r.read} # Expected: "\x{835C}" "xxx" # Actual: "\x{835C}xxx" "" ``` 2. Or, `limit < rs.bytesize` ```ruby IO.pipe{|r,w|w.write("a:bc"); w.close_write; p r.gets(":::", 2); p r.read} # Expected: "a:" "bc" # Actual: "a:bc" "" ``` This behavior appears to date back to Ruby 1.9.x. -- https://bugs.ruby-lang.org/