Actions
Bug #20280
closedError at invalid encoding symbols
Description
Parsing an invalid encoding symbol raises an EncodingError
.
It must be a SyntaxError
.
Updated by nobu (Nobuyoshi Nakada) 11 months ago
- Status changed from Open to Closed
Applied in changeset git|fcc55dc2261b4c61da711c10a5476d05d4391eca.
[Bug #20280] Raise SyntaxError on invalid encoding symbol
Updated by k0kubun (Takashi Kokubun) 8 months ago
The diff seems to conflict with refactoring changes that are missing in ruby_3_3
. Could you file a backport PR to ruby_3_3
branch?
Updated by k0kubun (Takashi Kokubun) 8 months ago
- Status changed from Closed to Open
Updated by k0kubun (Takashi Kokubun) 7 months ago
- Status changed from Open to Closed
Updated by peterzhu2118 (Peter Zhu) 7 months ago
I opened a PR for backport to 3.3: https://github.com/ruby/ruby/pull/10967
Updated by k0kubun (Takashi Kokubun) 7 months ago
- Backport changed from 3.0: REQUIRED, 3.1: REQUIRED, 3.2: REQUIRED, 3.3: REQUIRED to 3.0: REQUIRED, 3.1: REQUIRED, 3.2: REQUIRED, 3.3: DONE
ruby_3_3 4c50d23245689761e04db450ced9fe9fa76997d0.
Updated by nagachika (Tomoyuki Chikanaga) 7 months ago
- 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.
Actions
Like0
Like0Like0Like0Like0Like0Like0Like0Like0