When I run PHPUnit on my develop branch, I am met with this mysterious error:
1) Jetstream\DeleteAccountTest::test_user_accounts_can_be_deleted
RuntimeException: Session store not set on request.
I tried reverting to the main branch, clearing my vendor and composer-lock file, and still get the same issue. However, this is where the issue becomes a local issue and I have no idea why.
I still get the error running a local test of the main branch, but it passes its checks on GitHub actions.
However, one of my commits somehow caused this issue to affect GitHub actions on the develop branch, and it's impossible for me to test locally which change caused this glitch that is now afflicting my local tests.
The error appears to be caused by test_user_accounts_can_be_deleted, yet the test directly below is almost identical and doesn't cause an error.
I found this is because the DeleteUserForm livewire component is accessing $request->session(), and despite working perfectly fine as Laravel Jetstream boilerplate for the past few months, there is now some issue introduced that makes this unacceptable.
I'd appreciate another pair of eyes on this, it's pretty confusing and there don't appear to be any similar issues online about this.
When I run PHPUnit on my develop branch, I am met with this mysterious error:
I tried reverting to the main branch, clearing my vendor and composer-lock file, and still get the same issue. However, this is where the issue becomes a local issue and I have no idea why.
I still get the error running a local test of the main branch, but it passes its checks on GitHub actions.
However, one of my commits somehow caused this issue to affect GitHub actions on the develop branch, and it's impossible for me to test locally which change caused this glitch that is now afflicting my local tests.
The error appears to be caused by
test_user_accounts_can_be_deleted
, yet the test directly below is almost identical and doesn't cause an error.I found this is because the
DeleteUserForm
livewire component is accessing$request->session()
, and despite working perfectly fine as Laravel Jetstream boilerplate for the past few months, there is now some issue introduced that makes this unacceptable.I'd appreciate another pair of eyes on this, it's pretty confusing and there don't appear to be any similar issues online about this.