-
Notifications
You must be signed in to change notification settings - Fork 29
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
Serializable closure breaks the Symfony var-dumper #77
Comments
Heya, thanks for reporting. We'll need more info and/or code to debug this further. Can you please create a repository with the command below, commit the code that reproduces the issue as one separate commit on the main/master branch and share the repository here? Please make sure that you have the latest version of the Laravel installer in order to run this command. Please also make sure you have both Git & the GitHub CLI tool properly set up. laravel new bug-report --github="--public" Please do not amend and create a separate commit with your custom changes. After you've posted the repository, we'll try to reproduce the issue. Thanks! |
Okay, this seems more complicated than I thought, as I can't reproduce it with a simple example. There's obviously something more to it, I'll keep narrowing it down. It's not the first time I ran into this issue, so it's reproductible, I just need to find the root cause. |
I think I see what's going on and why I wasn't able to reproduce it before. This behavior is triggered by a specific code path, and only when working with task workers in Octane (or multiple PHP processes in general):
tl;dr: calling My workaround was to add |
@borys-p Can you detail all the commands / steps, I need to type locally so I can reproduce that issue? |
Closing this issue because it's inactive, already solved, old or not relevant anymore. Feel to open up a new issue if you're still experiencing this. |
Serializable Closure Version
1.3.1
PHP Version
8.2.8
Description
This issue is again related to an Exception, but in a more typical way: when you try to
dump()
an Exception with laravel-serializable-closure in the stack trace, it will break inside the Symfonyvar-dumper
:It's happening in the following part of
Symfony\Component\VarDumper\Caster\ExceptionCaster
, which attempts to analyze the stack trace:This seems to be an actual bug, as
dump()
is a standard tool in Laravel.Steps To Reproduce
As above, just
dump()
an Exception that's originated in the Serializable Closure.The text was updated successfully, but these errors were encountered: