Skip to content

SERVER-107969 Fix socket option update exceeding max value #1618

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

Closed
wants to merge 1 commit into from

Conversation

lijinzhong88
Copy link

@lijinzhong88
Copy link
Author

@kelly-cs Could you please help review this PR and merge it if everything looks good? Thanks!

@kelly-cs
Copy link
Contributor

Hey @lijinzhong88 - thanks for the pull request, and for making a SERVER ticket / signing the contributor's agreement. Initial thoughts (which I'll mirror to Jira) - it looks like this might already be fixed by SERVER-69063 in MongoDB 7.0.0+

It looks like it was backported to 5.0 but not 6.0. Will discuss further on the ticket

@kelly-cs
Copy link
Contributor

edit - I just took a look and I think we may have missed the window to get this into 6.0 since it's EOL in 3 days, and we've already cut our final release for it.

Since this looks like it's fixed in 7.0+, I'm going to close this for now

@kelly-cs kelly-cs closed this Jul 29, 2025
@lijinzhong88
Copy link
Author

@kelly-cs Thanks for your reply. But i think this fix PR is still worth merging into the 6.0 branch. I‘ve added a comment to the jira ticket, please take another look.

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.

2 participants