-
Notifications
You must be signed in to change notification settings - Fork 656
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
Uncaught JsonException: Malformed UTF-8 characters #7418
Comments
Hey @iHarshalAgarwal, can you reproduce the issue on https://psalm.dev ? |
Can you run psalm with --debug-by-line option and showing us the code around the last line before it crashes please? Is it normal to have non-utf8 chars in your application or do you think this is a bug? |
I can try to run it with debug.
|
Technically caused by 94395f1#diff-5c6baec3e76db9b3e112dfeb0e62e892f763b799629976361d7047212b256404R115 |
We did. You're using the branch that is under active development. Is there any reason you're not using a published release instead? |
I'm not sure how can I change it to point to release branch? Do you have any documentation or something that I can refer to?
|
Can you show us your composer.json? |
This is my composer.json content {
|
That should not work to install psalm properly I think. You should not name your composer.json "vimeo/psalm" and you should do a I'm not sure how you ended up with the current master branch available |
With "composer require --dev vimeo/psalm", do you mean, I should add it in the require section? "require": { |
My above code change failed with error "Could not parse version constraint dev: Invalid version string "dev"" I am trying with specific version now - "vimeo/psalm": "4.18.*" |
yeah, 4.18.* should do the trick |
Still the same issue :( No private keys supplied ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 60 / 885 (6%) |
There is something wrong somewhere with your environment. Composer intalled the correct version
But then, when you run Psalm, it says
where it should say 4.18.1. What is the command you use to run Psalm!? |
Ah! since I am using this in an enterprise GitHub, we manage it through a separate repository, which was pulling the Docker image without any tag. It usually takes around an hour to complete the scan. Is that normal or could be due to the number of files in our repository? |
The number of files Psalm report is going to be scanned is actually lower than we have in Psalm itself, and it takes less than a minute here: https://github.com/vimeo/psalm/runs/4868209297?check_suite_focus=true#step:4:4 One hour is awfully slow. What's the actual command line you're using to run Psalm? |
Ah, ok. |
|
Is there any documentation I could refer to setup these suggestions? |
threads: https://psalm.dev/docs/running_psalm/command_line_usage/#running-psalm-faster |
Thank you @orklah |
Can someone please guide me on the below issue?
Error:
The text was updated successfully, but these errors were encountered: