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
Webprofiler "Argument 2 passed to Symfony\Bundle\WebProfilerBundle\Twig\WebProfilerExtension::dumpData()" error #24804
Comments
I have the same issue. Can't use profiler. |
Can one of you create a small example project that allows to reproduce your issue? |
@xabbuh Yep I should be able to create one later this evening once out of work |
@xabbuh had some free time testcase is here https://github.com/limitstudios/beta2test Security webprofiler error is very touch and go whether it happens The doctrine webprofiler error happens logged in or out; or any section with database interaction; I have also added the test login in the README |
Thanks for providing the example. However, this does work for me. The only thing I changed locally was to use SQLite instead of MySQL. Can you debug what is tried to be dumped when you get this error? |
@xabbuh Yep I used MySQL I will get the exact version tomorrow. How would I go about getting the dump contents would the contents of the stack trace be enough? It’s quite large so do you want as a text or attached as a file? |
You could create a gist and link to it here. If you want to debug this yourself, I suggest to configure Xdebug and add a breakpoint that would allow you to inspect what is going on. |
Yes... I have same issue |
I have the same issue. |
Could any of you try to identify which of the Might be the same issue as in #23050 |
Could you try #24829 please? |
Created: doctrine/DoctrineBundle#730 |
For me the security panel was ok. I had only problem with doctrine. |
…rt decision.object being null (ogizanagi) This PR was merged into the 3.3 branch. Discussion ---------- [SecurityBundle] Fix the datacollector to properly support decision.object being null | Q | A | ------------- | --- | Branch? | 3.3 <!-- see comment below --> | Bug fix? | yes | New feature? | no <!-- don't forget to update src/**/CHANGELOG.md files --> | BC breaks? | no | Deprecations? | no <!-- don't forget to update UPGRADE-*.md files --> | Tests pass? | yes | Fixed tickets | #24804 <!-- #-prefixed issue number(s), if any --> | License | MIT | Doc PR | N/A Similar to #23050, when accessing a `Data` clone property through `__get()` and the value is `null` for instance, you'll really get `null` instead of a `Data` instance. The solution is to use `seek` instead whenever we access and try to use `profiler_dump` on a `Data` property that can be a simple scalar like `null` or `false`. AFAIK, `decision.object` is the only one here. Commits ------- 769a5f2 [SecurityBundle] Fix the datacollector to properly support decision.object being null
@ogizanagi @xabbuh #24829 does fix the security panel error, I will keep an eye on doctrine/DoctrineBundle#730 for any further testing needed |
Regarding the Doctrine panel, the exception is caused by the inclusion of WebProfilerBundle's table template: As a side effect of #23056, the table cannot be used anymore on arrays of strings. |
Using Symfony Flex with version 4.0.0-BETA2 with the composer.json below, when logging in or as anonymous and trying to access the doctrine section or security section of the web profiler returns the following error for both (all other sections are fine)
Type error: Argument 2 passed to Symfony\Bundle\WebProfilerBundle\Twig\WebProfilerExtension::dumpData() must be an instance of Symfony\Component\VarDumper\Cloner\Data, null given, called in /beta2/var/cache/dev/twig/01/0179a685ace86281d0a70ef66f92ed078b595a533f89935addc2d2832b7b3795.php on line 749
Type error: Argument 2 passed to Symfony\Bundle\WebProfilerBundle\Twig\WebProfilerExtension::dumpData() must be an instance of Symfony\Component\VarDumper\Cloner\Data, array given, called in /beta2/var/cache/dev/twig/48/48b45b978a28ff1cde1082d35a927d1cd986704029abdd25b28918c42e0516fe.php on line 630
Composer.json
The text was updated successfully, but these errors were encountered: