-
-
Notifications
You must be signed in to change notification settings - Fork 3k
Remove unused bandwidth-throttle/token-bucket package and upgrade symfony/monolog-bridge to 7.3 #15271
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 7.x #15271 +/- ##
=========================================
Coverage 66.40% 66.40%
Complexity 35205 35205
=========================================
Files 2318 2318
Lines 141895 141895
=========================================
+ Hits 94230 94231 +1
+ Misses 47665 47664 -1
🚀 New features to boost your workflow:
|
b37b4d7
to
a75a04a
Compare
5245c21
to
349ca83
Compare
e2dc8cf
to
17bbe25
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code changes looks great! Thank you! 👍
Description
The package
bandwidth-throttle/token-bucket
is not used anywhere in the codebase. It was likely a leftover dependency.It is blocking the upgrade to
symfony/monolog-bridge
7.3, as explained in #15268. That version requiresmonolog/monolog ^3
, which depends onpsr/log ^2 || ^3
. However,bandwidth-throttle/token-bucket
requiresmalkusch/lock ^1
, which only supportspsr/log ^1
, creating a conflict.The removal is documented in
UPGRADE-7.0.md
.After removing the unused package, the
composer install
test began failing. This was due toLogProcessor
receiving aMonolog\LogRecord
instance instead of an array. To resolve this,monolog/monolog
was upgraded to ^3 andsymfony/monolog-bridge to ^7.3
. TheLogProcessor
was then refactored to accept aLogRecord
object, and its corresponding unit test was updated to match the new behavior.📋 Steps to test this PR: