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

fix fatal error when exception was thrown #29483

Merged
merged 1 commit into from
Aug 19, 2020
Merged

fix fatal error when exception was thrown #29483

merged 1 commit into from
Aug 19, 2020

Conversation

rafal-kos
Copy link
Contributor

@rafal-kos rafal-kos commented Aug 11, 2020

Description (*)

In some specific cases method convertConfigTimeToUtc was throwing an exception. There was a bug in this part: incorrect params sent to Phrase constructor

Related Pull Requests

Manual testing scenarios (*)

  1. Try to convert date object from UTC to UTC

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)

Resolved issues:

  1. resolves [Issue] fix fatal error when exception was thrown #29525: fix fatal error when exception was thrown

@m2-assistant
Copy link

m2-assistant bot commented Aug 11, 2020

Hi @rafal-kos. 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

@rafal-kos
Copy link
Contributor Author

@magento run all tests

@ihor-sviziev ihor-sviziev self-assigned this Aug 12, 2020
@ihor-sviziev ihor-sviziev added Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Award: test coverage labels Aug 12, 2020
@magento-engcom-team
Copy link
Contributor

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

@magento-engcom-team
Copy link
Contributor

@rafal-kos thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository.

@engcom-Charlie
Copy link
Contributor

engcom-Charlie commented Aug 12, 2020

✔️ QA Passed

Manual test scenario:

  1. set general/locale/timezone to something except of UTC, for example America/Chicago
  2. get object of \Magento\Framework\Stdlib\DateTime\TimezoneInterface
  3. call convertConfigTimeToUtc with param for example new \DateTime('2016-10-10 10:00:00', new \DateTimeZone('UTC'))

Before:
We get an error that the object Phrase can't be created.
image

After:
We get an expected exception with the text from Phrase.
image

@engcom-Charlie engcom-Charlie added the QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) label Aug 12, 2020
@sidolov
Copy link
Contributor

sidolov commented Aug 13, 2020

@magento create issue

@ghost ghost added the Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. label Aug 13, 2020
@engcom-Alfa engcom-Alfa added QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope and removed QA: Ready to add to Regression Scope Should be analyzed and added to Regression Testing Scope(if applicable) labels Aug 17, 2020
@magento-engcom-team magento-engcom-team merged commit 710e381 into magento:2.4-develop Aug 19, 2020
@m2-assistant
Copy link

m2-assistant bot commented Aug 19, 2020

Hi @rafal-kos, 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.

@rafal-kos rafal-kos deleted the fix-timezone-exception-issue branch August 19, 2020 11:33
@sidolov sidolov added this to the 2.4.2 milestone Aug 20, 2020
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 Award: test coverage Component: Stdlib Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: accept QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[Issue] fix fatal error when exception was thrown
6 participants