Malformed UTF-8
Open
Nobody has claimed this yet.
greppable
testneeded
whateverable
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
In some cases we get errors like this:
Unhandled exception in code scheduled on thread 20
Malformed UTF-8
The source of it seems to be a Proc::Async from get-output sub.
Logically, one would want to use $proc.stdout(:enc<utf8-c8>) to make it work, but it only corrupts memory.
So the issue is not in whateverable, as I believe. There's something wrong with rakudo and it has to be rakudobugged, but right now I don't know what exactly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the get-output sub in Whateverable.pm6 and its Proc::Async use, then inspect the $proc.stdout(:enc) path mentioned in the report. Reproduce the malformed UTF-8 failure and narrow it to a minimal Rakudo case; done means the failure is sufficiently isolated for a Rakudo bug report.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100