-
Notifications
You must be signed in to change notification settings - Fork 13.9k
-
Notifications
You must be signed in to change notification settings - Fork 13.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error running command service_enum: ArgumentError invalid byte sequence in UTF-8 #15833
Comments
Hi! This issue has been left open with no activity for a while now. We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. |
I haven't tested this but it seems likely that this is a bug. Adding |
Confirmed.
|
On my test system the UTF-8 issue was caused by this service:
For whatever reason, the string contains mixed encodings. This string eventually makes its way to This issue could be patched in
See also: |
The crash should be fixed in the next release by #16729 I believe the underlying issue may be caused by Metepreter may be dropping bytes still; but I haven't replicated the specific scenario provided by bcoles |
Closing issue as release has now gone out. If still an issue feel free to open this up again. |
The text was updated successfully, but these errors were encountered: