Skip to content

MC-38105: Unable to set native session handler that is different from the one define in php.ini #30866

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

Merged
merged 5 commits into from
Nov 20, 2020

Conversation

engcom-Echo
Copy link
Contributor

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

  1. Fixes Unable to set native session handler that is different from the one define in php.ini after update to Magento 2.3 #24717

Manual testing scenarios (*)

See: #24717

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Nov 10, 2020

Hi @engcom-Echo. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@engcom-Echo engcom-Echo added Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Severity: S1 Affects critical data or functionality and forces users to employ a workaround. labels Nov 10, 2020
@engcom-Echo
Copy link
Contributor Author

@magento run all tests

@engcom-Echo
Copy link
Contributor Author

@magento run all tests

@ihor-sviziev
Copy link
Contributor

@magento run WebAPI Tests

@ihor-sviziev ihor-sviziev added Award: bug fix Auto-Tests: Covered All changes in Pull Request is covered by auto-tests labels Nov 11, 2020
Copy link
Contributor

@ihor-sviziev ihor-sviziev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For now the only one improvement is needed.

Also tests were failing, let's check results again after restart

$this->assertEquals('private_no_expire', $sessionConfig->getOption('session.cache_limiter'));
$this->assertEquals('explicit_save_path', $sessionConfig->getOption('session.save_path'));
$this->assertArrayHasKey('session.use_only_cookies', self::$isIniSetInvoked);
$this->assertEquals('1', self::$isIniSetInvoked['session.use_only_cookies']);
foreach ($sessionConfig->getOptions() as $option => $value) {
if ($option=='session.save_handler') {
$this->assertArrayNotHasKey('session.save_handler', self::$isIniSetInvoked);
if ($option == 'session.save_handler' && $value == 'user') {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if ($option == 'session.save_handler' && $value == 'user') {
if ($option === 'session.save_handler' && $value === 'user') {

@engcom-Echo
Copy link
Contributor Author

For now the only one improvement is needed.

Also tests were failing, let's check results again after restart

Thanks. I think that the failure of the tests will be repeated and we need to change the solution.

@ihor-sviziev
Copy link
Contributor

@engcom-Echo pls just merge latest changes from 2.4-develop. I believe these failures related to recent changes

@engcom-Echo engcom-Echo force-pushed the MC-38105 branch 2 times, most recently from a5596aa to 6ede3eb Compare November 12, 2020 15:17
@engcom-Echo
Copy link
Contributor Author

@magento run all tests

@magento-engcom-team
Copy link
Contributor

Hi @ihor-sviziev, thank you for the review.
ENGCOM-8460 has been created to process this Pull Request

@engcom-Kilo
Copy link
Contributor

@magento-engcom-team
Copy link
Contributor

@engcom-Kilo the pull request successfully imported.

@engcom-Oscar
Copy link

✔️ QA passed
Was checked case from Manual testing scenarios
Before:
main.CRITICAL: Warning: SessionHandler::read(): open(127.0.0.1:11211/sess_0imeeaqmnvemdg4e3h57tat0ik, O_RDWR) failed: No such file or directory (2) in../vendor/magento/framework/Session/SaveHandler/Native.php on line 22 {"exception":"[object] (Exception(code: 0): Warning: SessionHandler::read(): open(127.0.0.1:11211/sess_0imeeaqmnvemdg4e3h57tat0ik, O_RDWR) failed: No such file or directory (2) in ../vendor/magento/framework/Session/SaveHandler/Native.php on line 22 at ../vendor/magento/framework/App/ErrorHandler.php:61)"} []
✔️ After:
No errors on homepage and in Admin on backend

@m2-assistant
Copy link

m2-assistant bot commented Nov 20, 2020

Hi @engcom-Echo, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Component: Session Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: accept Release Line: 2.4 Severity: S1 Affects critical data or functionality and forces users to employ a workaround.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to set native session handler that is different from the one define in php.ini after update to Magento 2.3
6 participants