Use same(1.44.1) tokio version across the project#1603
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1603 +/- ##
=======================================
Coverage 21.92% 21.92%
=======================================
Files 135 135
Lines 9573 9573
=======================================
Hits 2099 2099
Misses 7474 7474
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Shourya742
left a comment
There was a problem hiding this comment.
Instead of making changes like these, we should focus on getting this merged: #1546.
#1546 is a profound change while this pr is just upgrading/aligning tokio versions. I dont see how they are related. Specifying a workspace dependency is similar to package dependencies except: Which is a deal breaker IMO. I would not block this one because of #1546, specially when we also have #1549 and others. #1549 #1546 and others needs further discussions and consensus before we merge them. |
Moreover, currently we align shared dependencies between crates by adding them to |
What I mean is that changes related to the unification of dependency versions are automatically resolved when any of the above-mentioned PRs get merged. Since these changes will eventually be removed within a couple of months, I don’t see the point in adding them, especially considering they are not blocking any of our current tasks. |
|
Hey @jbesraa, your PR cannot be rebased due to conflicts. Could you resolve them, please? |
|
Hey @jbesraa, your PR cannot be rebased due to conflicts. Could you resolve them, please? |
resolves #1596