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

Updated monolog/monolog to 2.26.1 #33226

Conversation

konarshankar07
Copy link
Contributor

@konarshankar07 konarshankar07 commented Jun 12, 2021

Depends on: magento/magento2-functional-testing-framework#832

Description (*)

Updated monolog/monolog to 2.26.1

Fixed Issues (if relevant)

  1. Fixes Update monolog/monolog to the latest version #32868

Related Pull Requests

https://github.com/magento/partners-magento2ee/pull/555

@m2-assistant
Copy link

m2-assistant bot commented Jun 12, 2021

Hi @konarshankar07. Thank you for your contribution
Here are 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 platform-health 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
  13. Semantic Version Checker

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

@m2-community-project m2-community-project bot added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Jun 12, 2021
@konarshankar07
Copy link
Contributor Author

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@konarshankar07
Copy link
Contributor Author

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@konarshankar07
Copy link
Contributor Author

@magento run Static Tests

@magento-automated-testing
Copy link

Pull Requests are not mergeable to the mainline. Please merge the latest mainlines to your Pull Requests and restart the builds.

@sivaschenko
Copy link
Member

sivaschenko commented Jun 19, 2021

Static tests are failing as the composer.json is not updated in EE repo

Are there any partner contributors volunteers to collaborate on this PR and create corresponding EE PR to fix static tests?

Added "help wanted" label for this purpose

Copy link
Member

@sivaschenko sivaschenko left a comment

Choose a reason for hiding this comment

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

Thanks for the pull request @konarshankar07 ! Please see my comment

composer.json Outdated
@@ -65,7 +65,7 @@
"magento/composer": "1.6.0",
"magento/magento-composer-installer": ">=0.1.11",
"magento/zendframework1": "~1.14.2",
"monolog/monolog": "^1.17",
"monolog/monolog": "~1.26.1",
Copy link
Member

Choose a reason for hiding this comment

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

Let's update monolog to the latest available version

Suggested change
"monolog/monolog": "~1.26.1",
"monolog/monolog": "^2.2",

@sivaschenko
Copy link
Member

Removed "help wanted" label, as @drpayyne has joined to help on the commerce repo side

@sivaschenko
Copy link
Member

This pull request depends on the MFTF changes (update of the same library)

@sivaschenko
Copy link
Member

EE pull request added to the related: https://github.com/magento/partners-magento2ee/pull/555

This pull request will be ready to merge once changes from magento/magento2-functional-testing-framework#832 are released

@sivaschenko
Copy link
Member

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@jilu1
Copy link
Contributor

jilu1 commented Jun 30, 2021

@sivaschenko
Is branch konarshankar07:update/package-monolog-1.26.1 ready with upgraded monolog tesing? I got failed build http://10.234.231.143:8080/job/Functional-Tests-CE/4100/.

Copy link
Member

@sivaschenko sivaschenko left a comment

Choose a reason for hiding this comment

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

Hi @konarshankar07 , can you please update the codebase for the latest monolog version.

Currently the tests are failing with error:

PHP Fatal error:  Declaration of Magento\Framework\Logger\Handler\Base::write(array $record) must be compatible with Monolog\Handler\StreamHandler::write(array $record): void in /var/www/html/lib/internal/Magento/Framework/Logger/Handler/Base.php on line 81

@@ -34,7 +34,7 @@
"laminas/laminas-uri": "^2.5.1",
"laminas/laminas-validator": "^2.6.0",
"magento/zendframework1": "~1.14.2",
"monolog/monolog": "^1.17",
"monolog/monolog": "~1.26.1",
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
"monolog/monolog": "~1.26.1",
"monolog/monolog": "^2.2",

@konarshankar07
Copy link
Contributor Author

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

@hostep
Copy link
Contributor

hostep commented Jul 15, 2021

Would love to see this happen, as monolog v2 comes with a new datetime format that includes timezone information.

I was just researching this topic accidentally before running into this PR, because I think it could be very helpful in reading log files and I always get confused about the timestamps in Magento log files because it's currently not clear what timezone they are representing.

Alternatively, if this upgrade would take too much time to get approved, we could change the second parameter of the LineFormatter object that is created over here to Y-m-d\TH:i:sP. That would also solve my need.

Just FYI 🙂

@andrewbess
Copy link
Contributor

Hello @hostep
We are actively working on updating the monolog to version 2.3.1 in new PRs.
This PR will be closed because of contributor doesn't continue working on this PR.
New PRs:
#33497
magento/magento2-functional-testing-framework#854

@sivaschenko
Copy link
Member

Closing in favour to finalized #33497

@m2-assistant
Copy link

m2-assistant bot commented Jul 21, 2021

Hi @konarshankar07, 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
has dependency Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Project: Platform Health
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants