Anatoly Pashin
Anatoly Pashin
This is a follow up for https://github.com/phpstan/phpstan/discussions/4359
Full description is in #206. TL;DR: encoding from boundary can be in different case than `mb_list_encodings()` output.
Such messages body is presented as `???` chars, instead of real chars. But subject is decoded as it should and have no problem. Here is message original: https://gist.github.com/b1rdex/387473a0d4f54e0c060388a7d876a31a
Fixes https://github.com/FriendsOfPHP/pickle/issues/247 Previous behavior: default to `latest` version, if no stability or version was requested. New behavior: default to `stable`.
``` /** * @ORM\Entity(repositoryClass=TrackerStatusRepository::class) */ class TrackerStatus { } ``` 1. Alt+Enter on `TrackerStatus` always has `add repository` QF if class is specified with constant 2. Find Usages of `TrackerStatusRepository`...
Please see original issue here: https://youtrack.jetbrains.com/issue/WI-42415 There is reproducible example. With your plugin enabled `$passwordManager` loses it's type.
Currently, there is no easy way to get a change log between the versions – only comparing commit by commit works. Providing tags would ease this.
There is huge memory leak in this: at least you don't terminate Workers and creating new each time.
We use kira-dependencies in self-hosted GitLab. It works well, but for one repository it yields a strange error: ``` [0KRunning with gitlab-runner 13.10.0 (54944146) [0;m[0K on infra-gitlab-runner-68856b776d-lx5qw 4SqrWnSc [0;m[0K feature...