Issue #20280 has been updated by peterzhu2118 (Peter Zhu). I opened a PR for backport to 3.3: https://github.com/ruby/ruby/pull/10967 ---------------------------------------- Bug #20280: Error at invalid encoding symbols https://bugs.ruby-lang.org/issues/20280#change-108797 * Author: nobu (Nobuyoshi Nakada) * Status: Closed * Backport: 3.0: REQUIRED, 3.1: REQUIRED, 3.2: REQUIRED, 3.3: REQUIRED ---------------------------------------- Parsing an invalid encoding symbol raises an `EncodingError`. It must be a `SyntaxError`. https://github.com/ruby/ruby/pull/10014 -- https://bugs.ruby-lang.org/

Issue #20280 has been updated by nagachika (Tomoyuki Chikanaga). Backport changed from 3.0: REQUIRED, 3.1: REQUIRED, 3.2: REQUIRED, 3.3: DONE to 3.1: REQUIRED, 3.2: WONTFIX, 3.3: DONE SyntaxErro isn't a descendant of StandardError and cannot be caught with rescue clause without explicit exception class specification. I won't backport this to 3.2 until any real world application suffered from this issue. ---------------------------------------- Bug #20280: Error at invalid encoding symbols https://bugs.ruby-lang.org/issues/20280#change-108829 * Author: nobu (Nobuyoshi Nakada) * Status: Closed * Backport: 3.1: REQUIRED, 3.2: WONTFIX, 3.3: DONE ---------------------------------------- Parsing an invalid encoding symbol raises an `EncodingError`. It must be a `SyntaxError`. https://github.com/ruby/ruby/pull/10014 -- https://bugs.ruby-lang.org/