What is this stacked request?

[ryanmortier]

Every time I hard reload, this stacked request shows up. As you can see it's an old request (the time). Have I turned something on by accident? How do I get rid of this?

[parallels999]

http://phpdebugbar.com/docs/ajax-and-stack.html#stacked-data

laravel-debugbar/tests/DebugbarBrowserTest.php

Lines 129 to 137 in 7fa0a65

	$this->browse(function (Browser $browser) {
	$browser->visit('web/redirect')
	->assertSee('PONG')
	->waitFor('.phpdebugbar')
	->assertSee('GET web/plain')
	->click('.phpdebugbar-tab-history')
	->waitForTextIn('.phpdebugbar-widgets-dataset-history', 'web/redirect (stacked)')
	->assertSee('web/redirect');
	});

[ryanmortier]

I don't think this was showing a few months ago. Has something changed?

[barryvdh]

I think that is probably from your session, or it's a redirect.
When you visit / and it redirects to maintanance, you actually have 2 requests, but never see the first. So that is stacked.

[ryanmortier]

I do have a redirect on the / route just to sign in but then I never hit that again.

Route::get('/', function () {
    Auth::login(User::first()); // just for local dev

    return Redirect::to(Filament::getPanel('maintenance')->getUrl());
});

[felabrecque]

@barryvdh Is there a better way to empty the "stacked data" then to logout/login (destroy the session) ?

I have a multi-language website, / redirect to either /fr or /en
On each subsequent webpage, the stack data will be shown.
And if I go again on the root url, another "stacked" entry is created.
The only way currently seems to destroy the session.

Clicking "clear" in the "request history" panel of the debugbar doesn't get rid of it (since it in the session I think)

[barryvdh]

Which version of Debugbar and Laravel?

[felabrecque]

Laravel: 10.48.28
Debugbar: 3.15.2

[ryanmortier]

I'm reopening because as of now this is completely unusable for me.

My request starts at 6 (a hard reload). Something has broken in the last month or two.

Laravel: v11.44.1
Debugbar: v3.15.2

[barryvdh]

Are you doing some custom session handling? Which session driver do you use?

[ryanmortier]

Nothing custom, using database driver.

edit: and sorry, I didn't mean to overstate the usability. I appreciate the package and it's usable, it's just an annoyance.

SESSION_DRIVER=database
SESSION_LIFETIME=120
SESSION_ENCRYPT=false
SESSION_PATH=/
SESSION_DOMAIN=null
SESSION_SECURE_COOKIE=true