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
[BUG] An error occurred while loading the query explanation. #830
Comments
Closing here - please open a new issue with more detailed information, examples, as well as what has been attempted so far, including tests that were written to uncover the issue. |
@Ocramius This is just a simple find query. Its also working well but the issue is related to query explanation Does it really needs to tests?? |
Well, it surely needs more debugging and searching for a root cause before reporting an issue 👍 |
Its a fresh Symfony project without any specific dependency that runs a simple select by 1 query. That's all. |
Yes: as I said, report a bug after:
|
Mostly just struggling with all the issues being juggled, hence the request for more details, as well as isolated scenarios. No malice intended, just be aware that I answer a dozen of these a day, and only get to look at anything ince it's already well distilled.
If you think sharing a repository would be the easiest reproducer, sure. The ideal case would be a setup from the first clone of the exact distribution and version of symfony you are using, and what you did from then on (line-by-line). |
All right. I will try my best to reproduce the issue step by step with detailed information. |
FYI this was fixed in #802, merged but not released yet. |
I think there must be a bug on query explanation doctrine.
Doctrine ^1.6
Symfony 4.1.1
I have a simple find query with doctrine. When I run my code everything works just fine. But when I try to run query explain on profiler there is the error:
An error occurred while loading the query explanation.
I have googled it and a lot of people have the same issue. But there is no fix. Any solution?
The text was updated successfully, but these errors were encountered: