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
[Session] Error when updating to 3.3.11 on session handler. #24941
Comments
Possibly related to #24934 |
@gmponos just to double-check... if you simply comment out the |
The smoke tests above are passing. I have to test further if the rest application works as expected since it's an API application. Is the session also started when I have an API in symfony? |
@gmponos Can you test the fix and confirm it solves your issue? |
Commenting this code part manually at 3.1.11 version passes the above smoke tests. I can't checkout to 2.* branch because my application is using 3.1.* Also my end-to-end (functional) tests are passing either having the code commented either not. |
Basically we need to be clear here. The above test all it does is getting the service ids and checks whether it can initiate the services. Maybe another service id initiated the session and that is why the above test is failing. I already have some Also this is my session config:
|
…kas, sroze) This PR was merged into the 2.7 branch. Discussion ---------- [HttpFoundation] Fix session-related BC break | Q | A | ------------- | --- | Branch? | 2.7 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #24941, #24934, #24947 and #24946 | License | MIT | Doc PR | - Conservative fix. Commits ------- 38186aa [HttpFoundation] Add test 3eaa188 [HttpFoundation] Fix session-related BC break
Hello there. I have the following test class.
The goal of this Test Class is to detect if in your Yaml if you have declared services in a wrong way. Something like this:
The above will throw a test error when it will try to fetch
app.myservice
.After updating to 3.3.11 my tests are failing because of this:
The text was updated successfully, but these errors were encountered: