Fix methods defined with invalid encoding are not displayed in completion #1101
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes a crash in IRB's method completion when a completion candidate contains characters that cannot be converted to
Encoding.default_external
.(#900)Problem
Currently, if a method or variable name includes characters incompatible with
Encoding.default_external
, triggering method completion results in anEncoding::UndefinedConversionError
, which crashes the entire IRB session. This leads to a poor user experience, as the session terminates unexpectedly and work can be lost.Solution
Instead of allowing the exception to crash the session, this change catches the encoding error and prints a warning message to stderr. To avoid flooding the console, this warning is displayed only once per session upon the first occurrence of the error.
This approach is preferable because it informs the user about the underlying encoding issue without abruptly ending their workflow.
Behavior Change