Skip to content
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

debug_backtrace limit #48

Open
vintagesucks opened this issue Apr 22, 2019 · 1 comment
Open

debug_backtrace limit #48

vintagesucks opened this issue Apr 22, 2019 · 1 comment
Labels
good first issue Good for newcomers

Comments

@vintagesucks
Copy link

Is there a special reason why the debug_backtrace() limit was set to 50?

$backtrace = collect(debug_backtrace(DEBUG_BACKTRACE_PROVIDE_OBJECT, 50));

I am in a situation where I am implementing recursive relationships and at a certain depth the following line throws an ErrorException (E_NOTICE) (Undefined offset: 0):

$key = md5($query->sql . $model . $relationName . $sources[0]->name . $sources[0]->line);

Increasing the debug_backtrace() limit makes the notice disappear (at least to a certain depth). Would it be possible to make the limit configurable/disableable or is there a better approach that I don't see right now?

Thank you.

@premmohantyagi
Copy link

Thank You
Issue is fixed by increase the debug_backtrace limit

@mpociot mpociot closed this as completed May 19, 2020
@mpociot mpociot reopened this May 19, 2020
@mechelon mechelon added the good first issue Good for newcomers label Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

4 participants