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

Update Finagle to 23.11 #573

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Update Finagle to 23.11 #573

wants to merge 3 commits into from

Conversation

milanvdm
Copy link
Member

@milanvdm milanvdm commented Nov 8, 2023

No description provided.

@milanvdm milanvdm requested a review from bpholt November 8, 2023 08:27
@milanvdm
Copy link
Member Author

milanvdm commented Nov 8, 2023

@bpholt Found the following MiMa issues:

[error] finagle-core: Failed binary compatibility check against com.twitter:finagle-core_2.12:23.11.0! Found 2 potential problems
[error]  * class com.twitter.finagle.context.Requeues does not have a correspondent in current version
[error]    filter with: ProblemFilters.exclude[MissingClassProblem]("com.twitter.finagle.context.Requeues")
[error]  * object com.twitter.finagle.context.Requeues does not have a correspondent in current version
[error]    filter with: ProblemFilters.exclude[MissingClassProblem]("com.twitter.finagle.context.Requeues$")

From what I can tell, these are not an issue. But that does mean I need to drop the 22.12.0 version in the MiMa check.

@bpholt
Copy link
Member

bpholt commented Nov 13, 2023

Yes, that sounds right.

Someday I'd like to introduce a scheme like I added to my company's async-utils library, where we publish different artifacts of catbird linked against each of several older versions of Finagle/Twitter Utils, but since we haven't really been introducing new features to catbird, I don't think that's pressing. (If there were new features included in the upcoming release, it would force users to also update their Twitter versions, which isn't always trivial.) For now I think we can update the upstream MiMa check and then we'll publish v23.11.0.

@milanvdm
Copy link
Member Author

@bpholt Done! :)

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (1043ccd) 90.60% compared to head (a70d912) 90.60%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #573   +/-   ##
=======================================
  Coverage   90.60%   90.60%           
=======================================
  Files          18       18           
  Lines         298      298           
  Branches        2        2           
=======================================
  Hits          270      270           
  Misses         28       28           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@milanvdm
Copy link
Member Author

milanvdm commented Dec 7, 2023

@bpholt Kind reminder! :)

@milanvdm
Copy link
Member Author

@bpholt Could I get an approval on this? :)

@nickrsabol
Copy link

@bpholt is there any intention on merging this please?

@nickrsabol
Copy link

Hi @bpholt thank you for your efforts in maintaining this project. It is used widely by teams at my company with great success. We are currently upgrading our dependencies on Finagle and are unable to do so until this project is brought up to date as well. Could this pull request please get merged so that we can make progress?

@milanvdm
Copy link
Member Author

@nickrsabol Ive raised this with Typelevel and hopefully get this merged :)

@bpholt
Copy link
Member

bpholt commented Jun 10, 2024

I'd like to spend some time on this this week, so we can resolve those MiMa issues without dropping the version from the check. Can we hold off on merging until that's done?

@bpholt
Copy link
Member

bpholt commented Jun 14, 2024

See #607 for some progress I made on this today. If that's deemed an acceptable approach, then once it's merged, we can add 23.11 to the list of supported Finagles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants