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.

Sign up for GitHub

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

Jump to bottom

chore: go 1.23(.2) #10540

Merged
merged 4 commits into from
Oct 8, 2024
Merged

chore: go 1.23(.2) #10540

merged 4 commits into from
Oct 8, 2024

Conversation

lidel
Copy link
Member

@lidel lidel commented Oct 7, 2024 •
edited
Loading

go1.23.2 includes potential fix for issue described in #10501

  • local A/B with 1.22 vs 1.23.2 confirming no regressions
    • no longer leaks connections
    • killing daemon via ^C works
  • docker
  • ci

Closes #10501

@lidel
chore: go1.23(.2)
cf364b8 
go1.23.2 includes potential fix for issue described in
#10501
@lidel lidel added the skip/changelog This change does NOT require a changelog entry label Oct 7, 2024
@lidel lidel changed the title chore: go1.23(.2) chore: go 1.23(.2) Oct 7, 2024
@lidel lidel marked this pull request as ready for review October 7, 2024 18:19
@lidel lidel requested a review from a team as a code owner October 7, 2024 18:19
@lidel lidel removed the skip/changelog This change does NOT require a changelog entry label Oct 7, 2024
@lidel lidel merged commit 091bc08 into master Oct 8, 2024
17 checks passed
@lidel lidel deleted the chore/go1.23.2 branch October 8, 2024 15:16
lidel added a commit that referenced this pull request Oct 8, 2024
@lidel
fix: go 1.23(.2) (#10540)
5985451 
go1.23.2 includes potential fix for issue described in
#10501

(cherry picked from commit 091bc08)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

go1.23 timers cause issues with libp2p connmgr and more
1 participant
@lidel